Instantiating a slice of a 5g or other next generation service network in an underserved area

ABSTRACT

Techniques for creating a service slice of a network in an underserved area are presented. A vehicle can be associated with a slice component that can generate service slices of a service network for various services. The vehicle can travel to an underserved area that does not have adequate wireless coverage or advance capabilities. For a communication device associated with an entity located in an underserved area, slice component can generate a service slice to connect the communication device to the communication network (and service network), establish a session with the communication device, provide applications, including VNF applications, to the communication device, and communicate information between the communication device and communication network (and service network). If no radio access to the network is available, slice component can continue the session with an internal slice and store information in its service database, which is synced when reconnected to the network.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/104,771, filed Aug. 17, 2018,and entitled “INSTANTIATING A SLICE OF A 5G OR OTHER NEXT GENERATIONSERVICE NETWORK IN AN UNDERSERVED AREA,” the entirety of whichapplication is hereby incorporated by reference herein.

TECHNICAL FIELD

The subject disclosure relates generally to communications networks,and, for example, to instantiating a slice of a 5G or other nextgeneration service network in an underserved area.

BACKGROUND

Communication devices, including wearable devices, sensory monitoringdevices, and other types of mobile or portable communication devices,can be utilized for a variety of purposes. For example, suchcommunication devices can be utilized in the healthcare industry tomonitor conditions of patients, collect information regarding conditionsof patients, and communicate such information to hospitals or otherhealthcare providers. When such communication devices are remotelylocated from a hospital or other healthcare provider, such communicationdevices typically have to be connected to a communication network inorder to communicate with a communication device of the hospital orother healthcare provider.

The above-described description is merely intended to provide acontextual overview relating to communication devices and communicationnetworks, and is not intended to be exhaustive.

BRIEF DESCRIPTION OF THE DRAWINGS

Various non-limiting embodiments are further described with reference tothe accompanying drawings in which:

FIG. 1 depicts a block diagram of an example, non-limiting system thatcan generate and manage slices of a service network for communicationdevices, in accordance with one or more embodiments described herein;

FIG. 2 illustrates a block diagram of another example, non-limitingsystem that can generate and manage slices of a service network forcommunication devices, in accordance with one or more embodimentsdescribed herein;

FIG. 3 depicts a block diagram of an example, non-limiting slicecomponent, in accordance with various aspects and embodiments of thedisclosed subject matter;

FIG. 4 illustrates a flow diagram of an example, non-limiting methodthat can generate and manage a slice of a service network for acommunication device, in accordance with various aspects and embodimentsof the disclosed subject matter;

FIG. 5 depicts a flow diagram of another example, non-limiting methodthat can generate and manage a slice of a service network for acommunication device, in accordance with various aspects and embodimentsof the disclosed subject matter;

FIG. 6 illustrates a flow diagram of an example, non-limiting method 600that, for a communication device, can generate and manage an internalslice of a local service network associated with a local (e.g., mobile)communication network associated with a vehicle or movable device, andsynchronize information between the local service network and a servicenetwork of a communication network, in accordance with various aspectsand embodiments of the disclosed subject matter;

FIG. 7 depicts an example block diagram of an example mobile deviceoperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein;

FIG. 8 illustrates a block diagram of an example access point, inaccordance with various aspects and embodiments of the disclosed subjectmatter; and

FIG. 9 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein.

DETAILED DESCRIPTION

One or more embodiments are now described more fully hereinafter withreference to the accompanying drawings in which example embodiments areshown. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the various embodiments. However, the variousembodiments can be practiced without these specific details (and withoutapplying to any particular network environment or standard).

Discussed herein are various aspects that relate to instantiating slices(e.g., service slice, core slice) of a 5G or other next generationservice network in an underserved area. By instantiating slices of a 5Gor other next generation service network in an underserved area, thedisclosed subject matter can significantly the provision of services ofa service network to a communication device in an underserved area andsecurely communicating data between the communication device in theunderserved area and the service network associated with a communicationnetwork (e.g., macro or small cell communication network), wherein theunderserved area can be, for example, an area that would otherwise havelimited or no connectivity to the communication network and associatedservice network, and/or no or inadequate advance capabilities, such as,for example, network slicing.

The various aspects described herein can relate to new radio, which canbe deployed as a standalone radio access technology or as anon-standalone radio access technology assisted by another radio accesstechnology, such as Long Term Evolution (LTE), for example. It should benoted that although various aspects and embodiments have been describedherein in the context of 5G, Universal Mobile Telecommunications System(UMTS), and/or Long Term Evolution (LTE), or other next generationnetworks, the disclosed aspects are not limited to 5G, a UMTSimplementation, and/or an LTE implementation as the techniques can alsobe applied in 3G, 4G, or LTE systems. For example, aspects or featuresof the disclosed embodiments can be exploited in substantially anywireless communication technology. Such wireless communicationtechnologies can include UMTS, Code Division Multiple Access (CDMA),Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), GeneralPacket Radio Service (GPRS), Enhanced GPRS, Third Generation PartnershipProject (3GPP), LTE, Third Generation Partnership Project 2 (3GPP2)Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA), EvolvedHigh Speed Packet Access (HSPA+), High-Speed Downlink Packet Access(HSDPA), High-Speed Uplink Packet Access (HSUPA), Zigbee, or anotherIEEE 802.XX technology. Such wireless communication technologies alsocan include Bluetooth™ or near field communication (NFC) technologies.Additionally, substantially all aspects disclosed herein can beexploited in legacy telecommunication technologies. Further, the variousaspects can be utilized with any Radio Access Technology (RAT) ormulti-RAT system where the mobile device operates using multiplecarriers (e.g., LTE Frequency Division Duplexing (FDD)/Time-DivisionDuplexing (TDD), Wideband Code Division Multiplexing Access(WCMDA)/HSPA, Global System for Mobile Communications (GSM)/GSM EDGERadio Access Network (GERAN), Wi Fi, Wireless Local Area Network (WLAN),WiMax, CDMA2000, and so on).

As used herein, “5G” can also be referred to as New Radio (NR) access.Accordingly, systems, methods, and/or machine-readable storage media forinstantiating slices (e.g., service slice, core slice) of a 5G or othernext generation service network in an underserved area, can be desired.As used herein, one or more aspects of a 5G network can comprise, but isnot limited to, data rates of several tens of megabits per second (Mbps)supported for tens of thousands of users; at least one gigabit persecond (Gbps) that can be offered simultaneously to tens of users (e.g.,tens of workers on the same office floor); several hundreds of thousandsof simultaneous connections supported for massive sensor deployments;spectral efficiency that can be significantly enhanced compared to 4G;improvement in coverage relative to 4G; signaling efficiency that can beenhanced compared to 4G; and/or latency that can be significantlyreduced compared to LTE.

Multiple Input, Multiple Output (MIMO) technology can be employed incommunication networks, wherein MIMO technology can be an advancedantenna technique utilized to improve spectral efficiency and, thereby,boost overall system capacity. Spectral efficiency (also referred to asspectrum efficiency or bandwidth efficiency) refers to an informationrate that can be transmitted over a given bandwidth in a communicationsystem.

For MIMO, a notation (M×N) can be utilized to represent the MIMOconfiguration in terms of a number of transmit antennas (M) and a numberof receive antennas (N) on one end of the transmission system. Examplesof MIMO configurations used for various technologies can include: (2×1),(1×2), (2×2), (4×2), (8×2) and (2×4), (4×4), (8×4). The configurationsrepresented by (2×1) and (1×2) can be special cases of MIMO known astransmit and receive diversity.

In some cases, MIMO systems can significantly increase the data carryingcapacity of wireless communications systems. Further, MIMO can be usedfor achieving diversity gain, which refers to an increase insignal-to-interference ratio due to a diversity scheme and, thus, canrepresent how much the transmission power can be reduced when thediversity scheme is introduced, without a corresponding performanceloss. MIMO also can be used to achieve spatial multiplexing gain, whichcan be realized when a communications system is transmitting differentstreams of data from the same radio resource in separate spatialdimensions (e.g., data is sent/received over multiple channels, linkedto different pilot frequencies, over multiple antennas). Spatialmultiplexing gain can result in capacity gain without the need foradditional power or bandwidth. In addition, MIMO can be utilized torealize beamforming gain. Due to the benefits achieved, MIMO can be anintegral part of the third generation wireless system and the fourthgeneration wireless system. In addition, 5G systems also will employmassive MIMO systems (e.g., hundreds of antennas at the transmitter sideand receiver side). Typically, with a (N_(t), N_(r)), where N_(t)denotes the number of transmit antennas and N_(r) denotes the number ofreceive antennas, the peak data rate can multiple with a factor of N_(t)over single antenna systems in a rich scattering environment.

To meet the significant demand for data centric applications, 3GPPsystems and systems that employ one or more aspects of thespecifications of the 4G standard for wireless communications can beextended to a 5G standard for wireless communications. Some uniquechallenges can exist to provide levels of service associated withforthcoming 5G, or other next generation, standards for wirelesscommunication.

Communication devices, including wearable devices, sensory monitoringdevices, and other types of mobile or portable communication devices,can be utilized for a variety of purposes. For example, suchcommunication devices can be utilized in the healthcare industry tomonitor conditions of patients, collect information regarding conditionsof patients, and communicate such information to hospitals or otherhealthcare providers. When such communication devices are remotelylocated from a hospital or other healthcare provider, such communicationdevices typically have to be connected to a communication network inorder to communicate with a communication device of the hospital orother healthcare provider.

For instance, a wearable communication device can monitor and recordinformation relating to virtually everything a user does. This caninclude movement of the user, one or more bodily readings, such as bloodsugar and/or heart rate of the user, and/or the humidity level when theuser was running on a treadmill. The recorded information relating tothe user can be directly transmitted to third-party servers or canbecome add-on metadata that can be used for number of diagnostic andstatistical application and services. However, there can be certain moreserious or significant healthcare related scenarios where theinformation collected from the communication devices of patients can bevital and personal, wherein there can be stringent measures forcollecting, communicating, and protecting such data in a secureHIPAA-compliant environment to maintain data integrity and patientconfidentiality. This disclosed subject matter can address such issuesand can describe how a closed and secure environment (e.g.,HIPAA-compliant environment or other secure environment) can be createdand used to collect and protect vital and personal information regardingusers (e.g., patients or other users).

To that end, the disclosed subject matter presents techniques, methods,and systems for creating a service slice of a network in an underservedor unserved area. A movable component (e.g., a vehicle or motorizeddevice) can comprise a slice component that can generate service slicesof a service network for various types of services and/or applications(e.g., healthcare-related services, law enforcement-related services,military-related services, farming-related services,agricultural-related services, transportation-related services,manufacturing-related services, construction-related services, . . . ).There can be underserved or unserved areas (e.g., rural or pastoralareas) where connectivity, such as wireless connectivity, to acommunication network and associated service network can be undesirablylimited or non-existent and/or advance capabilities, such as, forexample, network slicing, are not available or are not adequate.

The movable component (e.g., automobile or truck, ship, plane, dronedevice, robotic device, . . . ) can travel to an underserved or unservedarea that does not have any, or does not have adequate, wirelesscommunication coverage and/or advance capabilities. With regard to acommunication device associated with a user, a piece of equipment ormachine (e.g., tractor, plow, excavator, bulldozer, truck, tank, . . .), or other entity or object (e.g., a farm animal, a wild animal,)located in the underserved or unserved area, the slice component cangenerate a service slice (e.g., slice of a virtual network), andgenerate a corresponding core slice, to connect the communication deviceto the communication network (e.g., macro or small cell communicationnetwork) and associated service network, establish a session with thecommunication device, provide or facilitate providing applications,including virtual network function (VNF) applications, to thecommunication device, and communicate information between thecommunication device and the communication network and the associatedservice network.

In some embodiments, if no radio access (e.g., wireless communicationaccess) to the communication network is available, the slice componentcan continue the communication session with the communication device byusing an internal slice (e.g., internal service slice, and internal coreslice) and storing information relating to the communication session inthe service database of the slice component, wherein the databasecomponent (e.g., internal database component of the internal servicenetwork) of the slice component can be synced with the databasecomponent (e.g., main database component) of the service network whenthe slice component is reconnected to the communication network andassociated service network. For instance, there can be occasions wherethe slice component is not able to establish a communication connection,or can lose connection, to the communication network for a variety ofreasons (e.g., vehicle moved to a location where connection by the slicecomponent to the communication network is not able to be made and/orinterference with wireless communication between the slice component andthe communication network). On such occasions, the slice component canestablish or maintain a communication session with the communicationdevice, generate and maintain an internal slice of the service network,and provide or facilitate providing applications, including VNFapplications, to the communication device. The slice component can storeinformation relating to the communication session in the databasecomponent of the slice component (e.g., a local or “light” version ofthe main database component that can be maintained by the servicenetwork). When the slice component is able to connect or reconnect tothe communication network and the associated service network (e.g., whenthe vehicle moves to a location where connection to the communicationnetwork is possible and/or when connection to the communication networkis otherwise possible), the slice component can synchronize theinformation relating to the communication session in its databasecomponent with the main database component of the service network tostore the information relating to the communication session in the maindatabase component and/or to communicate certain information from theservice network (e.g., main database component of the service network)to the communication device.

These and other aspects and embodiments of the disclosed subject matterwill now be described with respect to the drawings.

FIG. 1 depicts a block diagram of an example, non-limiting system 100that can generate and manage slices of a service network forcommunication devices, in accordance with one or more embodimentsdescribed herein. The system 100 can comprise a communication network102 that can facilitate (e.g., enable) communications betweencommunication devices (e.g., UEs). The communication network 102 can beor can comprise, for example, a macro communication network, a smallcell communication network, or other type of communication network. Thecommunication network 102 can comprise or be associated with variouscomponents, such as network node devices (e.g., radio network nodedevices), routers, switches, interfaces, controllers, and/or othercomponents, that can facilitate communication of data betweencommunication devices in the communication network environment. Forexample, the communication network 102 can comprise or be associatedwith various (e.g., virtually any number of; virtually any type of)network node devices, such as network (NW) node device 104 (e.g., basestation, NodeB, eNodeB (e.g., evolved NodeB), or gNodeB (e.g., gNB)). Insome embodiments, the communication network 102 can comprise or beassociated with a cloud network. In certain embodiments, thecommunication network 102, including the network node devices and/orother components of or associated with the communication network 102,can employ MIMO technology to facilitate data communications betweendevices (e.g., network node devices, communication devices, . . . ) inthe communication network 102.

As used herein, the terms “network node device,” “network node,” and“network device” can be interchangeable with (or include) a network, anetwork controller or any number of other network components. Further,as utilized herein, the non-limiting term radio network node, or networknode (e.g., network device, network node device) can be used herein torefer to any type of network node serving communications devices and/orconnected to other network nodes, network elements, or another networknode from which the communications devices can receive a radio signal.In cellular radio access networks (e.g., universal mobiletelecommunications system (UMTS) networks), network devices can bereferred to as base transceiver stations (BTS), radio base station,radio network nodes, base stations, NodeB, eNodeB (e.g., evolved NodeB),and so on. In 5G terminology, the network nodes can be referred to asgNodeB (e.g., gNB) devices. Network devices also can comprise multipleantennas for performing various transmission operations (e.g., MIMOoperations). A network node can comprise a cabinet and other protectedenclosures, an antenna mast, and actual antennas. Network devices canserve several cells, and associated sectors (e.g., a sector can compriseone or more cells), depending on the configuration and type of antenna.Network node devices can be, for example, Node B devices, base station(BS) devices, access point (AP) devices, TRPs, and radio access network(RAN) devices. Other examples of network node devices can includemulti-standard radio (MSR) node devices, comprising: an MSR BS, agNodeB, an eNodeB, a network controller, a radio network controller(RNC), a base station controller (BSC), a relay, a donor nodecontrolling relay, a BTS, an AP, a transmission point, a transmissionnode, a Remote Radio Unit (RRU), a Remote Radio Head (RRH), nodes indistributed antenna system (DAS), and the like.

The communication network 102 can comprise a set of cells, whereinrespective cells can be associated with respective base stations (e.g.,network node device 104). For example, a radio access network (RAN) (notshown in FIG. 1) can comprise or be associated with a set of basestations that can serve communication devices located in respectivecoverage areas served by respective base stations in the communicationnetwork 102. In some embodiments, the RAN can be a cloud-RAN (C-RAN)that can be located in or associated with a cloud computing environment,comprising various cloud network components of the communication network102. The respective cells of the set of cells can have respectivecoverage areas that can form the coverage area covered by one or moresectors of the communication network 102. The respective communicationdevices can be communicatively connected to the communication network102 via respective wireless communication connections with one or moreof the respective cells.

The communication network 102 can comprise or be associated with a corenetwork and service network, wherein the core network can facilitateproviding wireless and other communication services to the coverage areacovered by the communication network 102, and wherein the servicenetwork can facilitate providing various applications and services, suchas, for example, service 106 and service 108, as well as applicationsrelating to such services. While two services (e.g., 106, 108) aredepicted in FIG. 1, it is to be appreciated and understood thatvirtually any desired number of services and applications can beprovided by the service network. The services and applications can bevirtually any type of service or application that is able to be providedvia the communication network 102 to communication devices associatedwith the communication network 102 and associated service network. Forexample, the services (and related applications) can be or relate tohealthcare-related services, law enforcement-related services,military-related services, finance-related services, farming-relatedservices, agricultural-related services, transportation-relatedservices, manufacturing-related services, construction-related services,machine-related services, equipment-related services, and/or other typesof services.

As described herein, the communication network 102 (e.g., macro and/orsmall cell communication network) can provide communication coverage(e.g., wireless communication coverage and services) to certain areas(e.g., certain geographical areas) to facilitate providing communicationservices, and other services (e.g., services (e.g., 106, 108) of theservice network) and applications, to communication devices in thosecertain areas. However, there can be other areas, such as underserved orunserved areas (e.g., rural, pastoral, other remote areas, or otherunderserved or unserved areas), where the communication network 102 istypically not able to provide communication services (e.g., wirelesscommunication coverage and services), and/or advance capabilities, suchas, for example, network slicing, to communication devices in such otherareas. Also, there can be instances where, even in the certain areas,the communication network 102 can be unable to provide any communicationcoverage or advance capabilities, or unable to provide desirable (e.g.,suitable, acceptable) communication coverage or advance capabilities, toa portion of the certain areas. For instance, one or more network nodedevices (e.g., base station, NodeB, eNodeB, or gNB) of or associatedwith the communication network 102 can be inoperable (e.g., temporarilyinoperable) or can be subject to interference that can prevent orinhibit (e.g., temporarily prevent or inhibit) the one or more networknode devices from providing communication coverage to the portion of thecertain areas. Consequently, the portion of the certain areas can be, atleast temporarily, underserved or unserved areas. As a result,communication devices in the unserved or underserved areas can be unableto access, or at least unable to desirably (e.g., suitably, acceptably,reliably) access the communication network 102 and associated servicenetwork, including the services (e.g., 106, 108), and associatedapplications, of the service network.

The disclosed subject matter can overcome these and other deficienciesrelating to providing communication coverage (e.g., wirelesscommunication coverage), advance capabilities (e.g., network slicing),and services (e.g., 106, 108) of the service network to communicationdevices in unserved or underserved areas, such as, for example,communication devices 110 and 112, which can be located in unserved orunderserved areas. The disclosed subject matter can employ a slicecomponent 118 that can provide or facilitate providing communicationcoverage and communication services, and services (e.g., 106, 108) andassociated applications of the service network via service slices, tocommunication devices (e.g., 110, 112) located in unserved orunderserved areas, as more fully described herein.

In some embodiments, the slice component 118 can be associated with(e.g., attached to, part of, integrated with, stored or stowed on, . . .) a movable component 120 (e.g., vehicle, motorized device, . . . ). Themovable component 120 can move the slice component 118 from location tolocation, such as moving the slice component 118 to an unserved orunderserved area where communication devices, such as communicationdevices 110 and/or 112, are located. The movable component 120 can bedirectly controlled by a user (e.g., a human user, or a non-human user)that is located on or within the movable component 120 or can beremotely controlled by a user (e.g., the movable component can be adrone that can be remotely controlled by a user using a remote controldevice associated with (e.g., communicatively connected to) the drone).The movable component 120 can be, for example, an automobile, a truck, aship or boat, a plane, a helicopter, a drone device, a robotic device, abicycle, a balloon (e.g., hot-air balloon), or other desired motorized,non-motorized, or manually movable vehicle or device. As an example, themovable component 120 can be a vehicle (e.g., truck, van, car, . . . ),associated with the slice component 118, that can travel to anunderserved or unserved area (e.g., a rural or pastoral area) to enablethe slice component 118 to connect with communication devices associatedwith other vehicles (e.g., tractors, trucks, bulldozers, . . . ) locatedin that underserved or unserved area. As some other examples, themovable component 120 can be a drone device or helicopter, associatedwith the slice component 118, that can fly (e.g., drone flying viaremote control), to an underserved or unserved area, over animalswearing communication devices (e.g., wearable collars or tags that arecommunication devices) that can communicate with the slice component118, or fly over vehicles (e.g., tractors, trucks, bulldozers, . . . )in an underserved or unserved area, wherein those vehicles can havecommunication devices associated therewith that can communicate with theslice component 118.

The respective communication devices (e.g., 110, 112) in the unserved orunderserved areas can be associated with respective entities, such as,for example, entity 114 and entity 116, respectively, wherein an entitycan be a user (e.g., a human being, or a non-human user), equipment, amachine, a device, an animal, a plant, or other type of entity. As someexamples, an entity (e.g., 114, 116) can be a person who has acommunication device (e.g., a mobile phone, computer, or wearabledevice); an animal (e.g., farm animal, wild animal, domesticated animal)wearing a communication device (e.g., a neck collar, tag, sensor, orother device having wireless communication functionality); a plantassociated with or in proximity to a communication device (e.g., acollar, tag, sensor, or other device having wireless communicationfunctionality); or equipment or a machine (e.g., tractor, plow,bulldozer, excavator, truck, . . . ) associated with a communicationdevice. A communication device (e.g., 110) can comprise or be associatedwith one or more sensors or instruments (e.g., healthcare-relatedsensors or instruments, farm or agricultural-related sensors orinstruments, transpiration-related sensor or instruments,environment-related sensors or instruments, military-related sensors orinstruments, law enforcement-related sensors or instruments, . . . )that can sense conditions or perform desired operations.

With further regard to communication devices, a communication device(e.g., 110, 112, . . . ) also can be referred to as, for example, adevice, a mobile device, or a mobile communication device. The term“mobile device” can be interchangeable with (or include) a UE or otherterminology. Mobile device (or UE) can refer to any type of wirelessdevice that can communicate with a radio network node in a cellular ormobile communication system. Examples of mobile devices can include, butare not limited to, a target device, a device to device (D2D) UE, amachine type UE or a UE capable of machine to machine (M2M)communication, a Personal Digital Assistant (PDA), a tablet or pad(e.g., an electronic tablet or pad), a mobile terminal, a cellularand/or smart phone, a computer (e.g., a laptop embedded equipment (LEE),a laptop mounted equipment (LME), or other type of computer), a dongle(e.g., a Universal Serial Bus (USB) dongle), an electronic gamingdevice, electronic eyeglasses, headwear, or bodywear (e.g., electroniceyeglasses, headwear, or bodywear having wireless communicationfunctionality), a device associated or integrated with a vehicle (e.g.,automobile, train, motorcycle, bicycle, ship, plane, . . . ), amotorized device (e.g., drone), or other entity, and so on.

It is noted that the various aspects of the disclosed subject matterdescribed herein can be applicable to single carrier as well as tomulticarrier (MC) or carrier aggregation (CA) operation of the mobiledevice. The term carrier aggregation (CA) also can be referred to (e.g.,interchangeably called) “multi-carrier system,” “multi-cell operation,”“multi-carrier operation,” “multi-carrier” transmission and/orreception. In addition, the various aspects discussed can be applied forMulti RAB (radio bearers) on some carriers (e.g., data plus speech issimultaneously scheduled).

With further regard to the slice component 118 and other aspects of thedisclosed subject matter, the slice component 118 can establish acommunication session with a communication device(s) (e.g., 110 and/or112), generate a service slice (e.g., slice of a virtual network) foruse by the communication device, and generate a corresponding core slicefor use by the communication device, to connect the communicationdevice(s) (e.g., 110 and/or 112) to the communication network 102 (e.g.,macro and/or small cell communication network) and associated servicenetwork, provide access to one or more services (e.g., 106 and/or 108)of the service network, provide or facilitate providing applications,including VNFs, associated with the one or more services to thecommunication device, and communicate information between thecommunication device and the communication network 102 and theassociated service network. In some embodiments, the slice component 118can coordinate with a network slice component 122 of the communicationnetwork 102 to facilitate generating slices for, providing access toservices (e.g., 106 and/or 108) to, and providing applications to,communication devices (e.g., 110 and/or 112), and communicatinginformation between the communication devices and the communicationnetwork 102 and the associated service network.

To facilitate establishing a communication session, the slice component118 can initiate, establish, or facilitate establishing (e.g.,generating) a communication connection between a communication device(e.g., 110) and the communication network 102 (e.g., a network device ofthe communication network 102 via a mobile network (NW) device 124(e.g., mobile network node device) of the slice component 118, forexample, when the movable component 120 and associated slice component118 are located (e.g., travel to be located) in proximity to (e.g.,within a defined distance of) the communication device (e.g., 110). Forinstance, the movable component 120, and associated slice component 118,can move to a location that is sufficiently in proximity to thecommunication device (e.g., 110) to enable a communication connection tobe established between the communication device (e.g., 110) and theslice component 118 (e.g., the mobile network device 124 of the slicecomponent 118) using a desired communication technology(ies) andassociated communication protocol(s). The communication technology(ies),and associated communication protocol(s), can be virtually anycommunication technology and associated protocol, such as, for example,any of the wireless communication technologies (and associatedcommunication protocols) disclosed herein.

The mobile network device 124 also can establish a connection with thenetwork node device 104 of the communication network 102 to facilitateestablishing the communication connection between the communicationdevice (e.g., 110) and the communication network 102 and associatednetwork slice component 122 (e.g., via the mobile network device 124 andthe network node device 104).

The slice component 118 can generate or facilitate generating a slice126 (e.g., service slice) of the service network, wherein the slice 126can be part of the service network associated with the communicationnetwork, and wherein the slice 126 can relate to a service and/orapplication provided by the service network. In some embodiments, theslice component 118 can coordinate with the network slice component 122of the service network to facilitate generating the slice 126 of theservice network. The slice component 118 also can comprise, beassociated with, and/or manage a mobile (e.g., local, internal) servicenetwork, wherein the mobile service network can comprise all or adesired portion of the applications and functionality (e.g., VNFs),scripts (e.g., code and other data for applications), data (e.g., datastored in the database component 128 (DB)), etc., of the service networkassociated with the communication network. In certain embodiments, basedat least in part on the generating of the slice 126 in the servicenetwork, the slice component 118 can generate a corresponding slice 126′(e.g., a corresponding or internal (int.) service slice) in the mobileservice network of the slice component 118, wherein the correspondingslice 126′ can be the same or substantially the same as the slice 126 ofthe service network when there is a communication connection establishedbetween the slice component 118 and the communication network 102.

The slice component 118 also can coordinate with the network slicecomponent 122 of the service network to facilitate generating a coreslice 130 of the core network of the communication network 102. Theslice component 118 also can comprise a mobile core network. In someembodiments, in connection with generating the core slice 130 of thecore network, the slice component 118 can generate a corresponding coreslice 130′ (e.g., internal (int.) core slice) in the mobile core networkof the slice component 118, wherein the corresponding core slice 130′can be the same or substantially the same as the core slice 130 of thecore network when there is a communication connection establishedbetween the slice component 118 and the communication network 102.

As part of generating the slices 126 and 130 (and associated slices 126′and 130′) and establishing the communication connection, the slicecomponent 118 can create a secure communication channel between thecommunication device (e.g., 110) and the service network (e.g., aservice network device of the service network) via the mobile networkdevice 124, wherein the secure communication channel can be used tosecurely communicate information between the communication device (e.g.,110) and the service network via the mobile network device 124. Thesecure communication channel can enable secure communication ofinformation between the communication device (e.g., 110) and the servicenetwork via the mobile network device 124, in accordance with applicabledefined security criteria. The slice component 118 and/or the networkslice component 122 can provide applications, such as VNFs, and otherresources that can be utilized to create and provide the securecommunication channel, in accordance with the applicable definedsecurity criteria.

The defined security criteria can be based at least in part on the typeof service and the security specifications and protocols associated withthe service (e.g., service 106 or 108). For example, with regard to ahealthcare-related service, the defined security criteria can relate toHealth Insurance Portability and Accountability Act (HIPAA)specifications and protocols. The slice component 118 and/or the networkslice component 122 can provide applications, such as VNFs, and otherresources that can be utilized to create and provide a securecommunication channel that is in compliance with HIPAA specificationsand protocols, in accordance with the applicable defined securitycriteria. As another example, for a military-related service, thedefined security criteria can relate to military specifications andprotocols for communications (e.g., wireless communications of voice ordata traffic). The slice component 118 and/or the network slicecomponent 122 can provide applications, such as VNFs, and otherresources that can be utilized to create and provide a securecommunication channel that is in compliance with military specificationsand protocols, in accordance with the applicable defined securitycriteria. Other respective security criteria (e.g., security criteriarelating to law enforcement-related service, security criteria relatingto an agricultural-related service, security criteria relating to afarming-related service, . . . ) relating to other respectivespecifications and protocols of other services can define the structureand security that the secure communication is to have in order to complywith the respective security criteria of the other services. The definedsecurity criteria can be part of defined slice management criteria thatcan be employed to facilitate managing the creation and use of slices(e.g., service slices, internal service slices, core slices, internalcore slices) by the slice component 118 and/or communication network 102to facilitate securely communicating information (e.g., informationrelating to services) between the communication network 102 (e.g.,services associated with the communication network 102) and the slicecomponent 118 and associated communication devices (e.g., 110 and/or112, . . . ) and/or between the slice component 118 and associatedcommunication devices.

The slice component 118, employing the service slice 126 (and/orcorresponding service slice 126′) and core slice 130 (and/orcorresponding core slice 130′), the mobile service network, and thesecure communication channel, can provide (e.g., make available),facilitate providing, communicate, or facilitate communicating, all or adesired portion of the applications, functionality, resources, and/orinformation (e.g., service-related data, software or firmware updates, .. . ) associated with the service network (e.g., for the desired serviceof the service network) to the communication device (e.g., 110), via thesecure communication channel, to facilitate enabling the communicationdevice to utilize the desired service associated with the slice 126 in adesirably (e.g., optimally, suitably, or acceptably) secure environment.For instance, in addition to the VNFs and resources utilized to createthe secure communication channel, the slice component 118 can provide,or facilitate providing, desired VNFs, resources, and/or informationfrom the service network to the communication device (e.g., 110), viathe secure communication channel to facilitate enabling thecommunication device to utilize the desired service, application,resources, functions, etc., and exchange information with the servicenetwork in a desirably secure environment. From the standpoint of thecommunication devices (e.g., 110, 112, . . . ), the slice component 118,and associated mobile service network and mobile core network, canessentially be viewed as the communication network 102 (e.g., the slicecomponent 118, and associated mobile service network and mobile corenetwork, can be part of the communication network 102).

For example, if the communication device (e.g., 110) is associated with(e.g., attached to, integrated with, stowed on) a tractor on a ruralfarm, and the service (e.g., 106) is a farming-related serviceassociated with an entity that desires to collect information regardingthe operation of the tractor and/or the area being farmed using thetractor, the communication device (e.g., 110) can obtain information(e.g., statistics, information relating to conditions associated withthe farm or tractor, status information, . . . ) from sensors of orassociated with the communication device and/or tractor and cancommunicate such information to the service network via the securecommunication channel. The service network (e.g., the network slicecomponent 122 associated with the service network) can store suchinformation in the database component 128 or other desired data store.The slice component 118 also can store such information in a mobiledatabase component 132 (MDB) (e.g., a virtual database) of the mobileservice network to facilitate maintaining synchronization between themobile service network (and mobile database component 132) and theservice network (and database component 128).

As another example, if there is a software update or firmware updateavailable, the service network (e.g., via the network slice component122) can communicate information regarding the software update orfirmware update to the communication device (e.g., 110) via the securecommunication channel, and the software update or firmware update can beperformed at the communication device. If there is data (e.g.,service-related data) that the service network desires to communicate tothe communication device (e.g., 110), the service network cancommunicate such data to the communication device via the securecommunication channel

In some embodiments, employing the slices, the slice component 118, viathe mobile network device 124, can communicate with each of thecommunication devices (e.g., 110, 112, . . . ) to collect respectiveinformation from the respective communication devices to communicate tothe service network, and communicate other respective information (e.g.,service-related data, software or firmware updates, . . . ) from theservice network to the respective communication devices. In otherembodiments, one (or more) of the communication devices (e.g.,communication device 110) can collect information from the othercommunication devices (e.g., communication device 112 and/or othercommunication devices). For example, the communication (e.g., 110) canengage in ad hoc communication with the other communication devices(e.g., communication device 112 and/or other communication devices). Thecommunication device (e.g., 110), which collected the information fromthe other communication devices, can communicate its information and theinformation collected from the other communication devices to theservice network via the secure communication channel enabled byemploying the slices, the slice component 118, and the mobile networkdevice 124. Other information to be sent to the communication devicescan be communicated via the secure communication channel to thecommunication device (e.g., 110), and that communication device candistribute respective information to the other respective communicationdevices (e.g., communication device 112 and/or other communicationdevices).

As yet another illustrative example, it can be desirable (e.g.,important, legally required, specified in policy or specifications, . .. ) to maintain certain data (e.g., vital data, sensitive data, privatedata, proprietary or secret data, medical data, military data, and/orlaw enforcement data, . . . ) within a secure network, and avoid,minimize, or prohibit moving such data to Wi-Fi or other less securenetworks (e.g., as an interim access solution). Traditional techniquesand networks can have limited and/or insufficient capabilities todesirably (e.g., optimally, suitably, or acceptably) secure such datawithin a secure network.

The disclosed subject matter can employ the enhanced techniques,systems, methods, techniques, as disclosed and described herein, todesirably maintain and/or communicate such data within a secure network(e.g., via a secure network channel). In accordance with variousembodiments, the slice component 118 can create a slice (e.g., serviceslice 126) of a virtual network with all of the desired functions (e.g.,VNFs, applications, . . . ) to enable the communication device (e.g.,110) and/or associated entity (e.g., 114), which can be a user,equipment, animal, or other entity, to securely login to the servicenetwork (and associated communication network 102), start acommunication session with regard to the desired service (e.g., 106),generate the slice (e.g., service slice 126) of the service network (andcorresponding core slice 130 of the core network), and securelycommunicate information (e.g., sensor data) to the slice (e.g., serviceslice 126) of the service network via the secure communication channelcreated for the slice. For instance, in the case of a healthcare serviceprovider associated with the service (e.g., 106), the communicationdevice (e.g., 110) can comprise or be associated with one or moresensors that can sense conditions associated with the entity (e.g.,114). The communication device (e.g., 110), using the securecommunication channel associated with the slice (e.g., service slice126), can securely communicate the sensor data relating to the sensedconditions to the service network (e.g., to the slice 126 of the servicenetwork) for secure storage in the database component 128 and/or secureaccess by the healthcare service provider, in accordance with thedefined security criteria (e.g., HIPAA criteria). Thus, when an entity(e.g., patient) has or is provided a communication device (e.g., 110),the slice component 118 can provide the communication device (e.g., 110)and associated entity (e.g., 114) with the desired VNF applications tocreate an end-to-end slice (e.g., service slice 126) of the networkwithin the device hardware of the communication device with the abilityto have radio access (e.g., wireless communication access) to thecommunication network 102 (e.g., macro and/or small cell communicationnetwork), for example, when the slice component 118 is able to establisha communication connection with the communication network 102 andassociated service network (e.g., as business as usual (BAU)). In aninstance when a communication connection with the communication network102 and associated service network is not able to be established (or isdisrupted), the slice component 118 can continue the communicationsession using an internal slice (e.g., internal service slice 126′), canprovide all or at least a portion of the functionality (e.g., VNFapplications, resources, . . . ) and/or service-related informationassociated with the service (e.g., 106), can receive information fromthe communication device in connection with the service, and can storethe received information in the mobile database component 132, as morefully described herein. Once the mobile network device 124 of the slicecomponent 118 is able to connect or re-connect with the communicationnetwork 102 and associated service network, the slice component 118 cansynchronize (e.g., securely synchronize via a secure communicationchannel) information relating to the communication session with theservice network (e.g., information in the mobile database component 132can be synchronized with information in the database component 128), asmore fully described herein.

In some embodiments, the slice component 118 can generate or maintain,or facilitate generating or maintaining, (e.g., simultaneously or inparallel) multiple slices (e.g., multiple service slices, multiple coreslices, multiple internal service slices, and/or multiple internal coreslices) for respective communication devices (e.g., 110 and/or 112, . .. ) and/or respective services (e.g., 106 and/or 108, . . . ). Forexample, the slice component 118 can generate or maintain, or facilitategenerating or maintaining, a first set of slices (e.g., first serviceslice, first core slice, first internal service slice, and/or firstinternal core slice) for a first communication device (e.g., 110) withregard to a first service (e.g., 106); and, simultaneously or inparallel with the first set of slices, can generate or maintain, orfacilitate generating or maintaining, a second set of slices (e.g.,second service slice, second core slice, second internal service slice,and/or second internal core slice) for a second communication device(e.g., 112) with regard to a second service (e.g., 108) or the firstservice (e.g., 106). As another example, the slice component 118 cangenerate or maintain, or facilitate generating or maintaining, a firstset of slices (e.g., first service slice, first core slice, firstinternal service slice, and/or first internal core slice) for the firstcommunication device (e.g., 110) with regard to a first service (e.g.,106); and, simultaneously or in parallel with the first set of slices,can generate or maintain, or facilitate generating or maintaining, asecond set of slices (e.g., second service slice, second core slice,second internal service slice, and/or second internal core slice) forthe first communication device (e.g., 110) with regard to a secondservice (e.g., 108).

In some instances, the slice component 118 and associated mobile networkdevice 124 may not be able to establish a communication connection withthe communication network 102, or may lose a communication connectionwith the communication network, for example, due to problems with thecommunication network 102, interference between the mobile networkdevice 124 and the communication network 102 (e.g., the network nodedevice 104 of or associated with the communication network 102), and/orother issues. The disclosed subject matter can mitigate or overcome suchissues, as the slice component 118, employing the mobile service networkand mobile core network, can operate in place of, and can provide all orat least virtually all of the services, applications, functions, andresources of the service network, to the communication devices (e.g.,110, 112, . . . ) via the mobile service network of the slice component118.

For instance, in response to determining that the mobile network device124 is unable to establish a communication connection with thecommunication network 102 or determining that a communication connectionbetween the mobile network device 124 and the communication network 102has been lost (e.g., has dropped, failed, or otherwise beendisconnected), the slice component 118, and associated mobile servicenetwork and mobile core network, can start a communication session (inthe former case) or can continue a communication session (in the lattercase), acting on behalf of, or in place of, the communication network102 and associated service network and core network. With regard to anew communication session, the slice component 118, employing the mobilenetwork device 124 of the mobile (e.g., local, internal) core network,can establish a communication connection between the communicationdevice (e.g., 110) and the mobile network device 124. With regard to anongoing communication session, the slice component 118, employing themobile network device 124, can maintain the communication connectionbetween the communication device (e.g., 110) and the mobile networkdevice 124.

The slice component 118 can generate (or maintain) an internal slice,such as slice 126′, associated with the mobile service network, whereinthe internal slice 126′ can be part of the mobile service network, whichcan be associated with the mobile network device 124. The slicecomponent 118 also can generate or facilitate generating (ormaintaining) a corresponding internal core slice, such as core slice130′, of the mobile core network associated with the mobile networkdevice 124. The slice component 118, employing the internal slice 126′and the internal core slice 130′, can facilitate creating a securecommunication channel, based at least in part on (e.g., in accordancewith) the applicable defined security criteria relating to the service(e.g., 106 or 108) that the communication device (e.g., 110) desires toaccess and utilize.

The slice component 118 can maintain all or a desired portion of theinformation of the database component 128 of the service network in themobile database component 132 of the mobile service network to enablethe slice component 118 to be able to provide all, virtually all, or atleast most of the service features, service-related applications (e.g.,VNF applications), service-related functions, service-related data,etc., of the service(s) (e.g., 106 or 108) desired by the communicationdevice (e.g., 110). In accordance with various embodiments, the mobiledatabase component 132 can be a full (or at least substantially full)version, or a “light” version, of the database component 128, whereinthe “light” version can include a desired portion (e.g., a significantportion, but not all) of the information stored in the databasecomponent 128. The slice component 118 (e.g., the mobile service networkof or associated with the slice component 118) can comprise all or adesired portion of the applications and functionality (e.g., VNFs),scripts (e.g., code and other data for applications), and/or otherinformation of the service network associated with the communicationnetwork 102. From the perspective of the communication devices (e.g.,110, 112, . . . ), the slice component 118 and associated mobile servicenetwork, mobile core network, mobile database component 132, etc.,essentially can be and act like the communication network 102 andassociated service network, core network, database component 128, etc.

Utilizing the internal slice 126′ and associated internal core slice130′, information can be communicated, via the secure communicationchannel and mobile network device 124, from the communication device(e.g., 110) to the mobile service network of the slice component 118.Such information can comprise, for example, information relating to theservice (e.g., 106, or 108, . . . ) and/or entity (e.g., 114) associatedwith the communication device (e.g., 110). When the communication device(e.g., 110) is coordinating with and/or acting on behalf of othercommunication devices (e.g., 112) associated with other entities (e.g.,116), such information also can comprise other information obtained fromsuch other communication devices (e.g., 112) associated with such otherentities (e.g., 116). The slice component 118 can store the information,which is received from the communication device (e.g., 110) (or othercommunication device(s)), in the mobile database component 132associated with the mobile service network or other desired data store,as applicable and appropriate.

In some embodiments, the mobile service network of the slice component118 can have a software update(s), a firmware update(s), and/or otherdata (e.g., service-related data), associated with the service (e.g.,106, or 108, . . . ) being accessed by the communication device (e.g.,110), stored in the mobile database component 132 or other data store ofthe slice component 118. Utilizing the internal slice 126′ andassociated internal core slice 130′, the slice component 118 cancommunicate, via the secure communication channel and mobile networkdevice 124, the software update(s), firmware update(s), and/or otherdata to the communication device (e.g., 110). The communication device(e.g., 110) can perform the software update(s) and/or firmwareupdate(s), and/or can utilize or process the other data as appropriate.If the mobile service network does not have such software update(s),firmware update(s), and/or other data available to it (e.g., stored inthe mobile database component 132 or other data store), such update(s)and/or other data can be communicated to the communication device (e.g.,110) when the communication connection (and secure communicationchannel) is established or re-established with the communication network102 and associated service network and core network.

The slice component 118 and/or mobile network device 124 can monitor thecommunication network 102 and/or communication conditions in connectionwith attempting to establish or re-establish a communication connectionwith the communication network 102. Based at least in part on themonitoring (and/or, e.g., the results of analyzing data relating tocommunication conditions associated with the communication network 102),at some point in time, the slice component 118, employing the mobilenetwork device 124, can determine that a communication connection can beestablished or re-established between the mobile network device 124 andthe communication network 102 (e.g., macro and/or small cellcommunication network) and associated service network and core network,as well as services (e.g., 106, or 108, . . . ) and associatedapplications. For example, the movable component 120 (e.g., a vehicle,or motorized or movable device) associated with the slice component 118can move to a location where the mobile network device 124 is able toconnect to the communication network 102 and/or interference that wasinhibiting connection between the mobile network device 124 and thecommunication network 102 can be mitigated, reduced, or removed (e.g.,whether or not the movable component 120 moves to a different location).In response to determining that a communication connection can beestablished or re-established between the mobile network device 124 andthe communication network 102, the slice component 118 can establish orre-establish the communication connection (e.g., wireless communicationconnection), including a secure communication channel, between themobile network device 124 and the communication network 102 andassociated service network, core network, services, etc., and/or betweenthe communication device (e.g., 110) and the communication network 102and associated service network, core network, services, etc. (e.g., ifthe communication session of the communication device (e.g., 110) isstill in progress)).

In connection with establishing or re-establishing the communicationconnection with the communication network 102, the slice component 118(e.g., coordinating with the network slice component 122) can facilitategenerating the slice 126 and associated core slice 130, as more fullydescribed herein. If the communication session, which had been using theinternal slice 126′, is still in progress, the communication session cancontinue using the internal slice 126′ (e.g., internal service slice)and associated internal core slice 130′, in conjunction with using theslice 126 and associated core slice 130. The network slice component 122can comprise, be associated with, and/or manage the service network,wherein the service network can comprise the applications andfunctionality (e.g., VNFs), scripts (e.g., code and other data forapplications), information (e.g., information stored in the databasecomponent 128), services (e.g., 106, 108, . . . ), etc., of the servicenetwork.

With regard to the communication session (or portion of thecommunication session) that was occurring while the slice component 118(and communication device (e.g., 110) was not connected to thecommunication network 102, in response to establishing orre-establishing the communication connection and secure communicationchannel with the communication network 102, the slice component 118,employing the mobile network device 124 and the secure communicationchannel, can facilitate communicating information relating to thecommunication session (or portion thereof) associated with thecommunication device (e.g., 110) to the service network, and/orreceiving other information from the service network for storage in themobile service network (e.g., mobile database component 132 or otherdata store) and/or for communication to the communication device, tosynchronize information between the service network (e.g., the databasecomponent 128 of the service network) and the mobile service network(e.g., the mobile database component 132 of the mobile service network)and/or to provide the other information, or a portion thereof, to thecommunication device (e.g., 110) in connection with the communicationsession. Such other information can be determined (e.g., by the networkslice component 122), for example, based at least in part on (e.g., inresponse to) the information relating to the communication session (orportion thereof) communicated to the service network and/or the resultsof analyzing the information relating to the communication session.

The disclosed subject matter (e.g., employing the slice component 118and other components, as described herein) can employ enhancedtechniques, systems, and methods that can facilitate desirably providingcommunication coverage and/or advanced capabilities (e.g., networkslicing) in underserved or unserved areas, providing desirably securecommunication of information relating to services (e.g., wherein acommunication device does not have to leave the communication/servicenetwork, which can facilitate secure communication of informationbetween the communication device and service network), and providingdesirable (e.g., suitable, applicable, or optimal) data andcommunication security with respect to a particular service (e.g.,healthcare-related service, military-related service, lawenforcement-related service, . . . ), as more fully described herein.For instance, in some embodiments, with regard to certain securitysituations and/or services or entities that can desire relatively highsecurity of data in the network, the slice component 118 and othercomponents of the system 100 can employ desirably secure triplet andquadruple security functions and measures to secure data associated withthe service network, in accordance with the applicable defined securitycriteria. The disclosed subject matter can be a cost-effective solutionto dynamically extend network coverage (e.g., communication and/orservice network coverage) on demand for at least a certain desirableamount of time.

Referring to FIG. 2, FIG. 2 illustrates a block diagram of anotherexample, non-limiting system 200 that can generate and manage slices ofa service network for communication devices, in accordance with one ormore embodiments described herein. The system 200 can comprise a slicecomponent 202 and a communication network 204 that can be associatedwith the slice component 202, at least at certain times, via the networknode device 206 (e.g., base station, nodeB, eNodeB, or gNB).

The communication network 204 can comprise the core and service networks208. The communication network 204 (e.g., the service network of thecommunication network 204) can be associated with and/or can providevarious services, including service 210 and service 212, and associatedapplications, such as those disclosed herein. The communication network204 also can comprise a network slice component 214 that can communicateand coordinate with the slice component 202 to generate service slices,such as service slice 216, and core slices, such as core slice 218, asmore fully described herein, wherein the service slices and core slicescan be associated with the network slice component 214. The serviceslices, such as service slice 216, also can include or be associatedwith (e.g., communicatively connected to) database components, such as adatabase component 220.

The slice component 202 can comprise a mobile network device 222. Theslice component 202 also can comprise mobile core and service networks224. The slice component 202 can generate internal service slices, suchas internal service slice 216′, and internal core slices, such asinternal core slice 218′, as more fully described herein. The internalservice slices, such as internal service slice 216′, can comprise or beassociated with mobile database components, such as mobile databasecomponent 226. In some embodiments, the mobile database component 226can be a virtual database. The slice component 202 further can beassociated with a movable component 228 that can be employed to move theslice component 202 to various desired locations to enable the slicecomponent 202 to connect and communicate with communication devices,such as communication devices 230, 232, and/or 234, when the movablecomponent 228 moves the slice component 202 to a location that is inproximity to the slice component 202, as more fully described herein.

The respective components (e.g., slice component 202, communicationnetwork 204, network node device 206, core and service networks 208,network slice component 214, service slice 216, core slice 218, databasecomponent 220, mobile network device 222, mobile core and servicenetworks 224, internal service slice 216′, internal core slice 218′,mobile database component 226, movable component 228, communicationdevices (e.g., 230, 232, and/or 234), . . . ) of the system 200respectively can be the same as or similar to, and/or can comprise thesame or similar functionality as, respectively named components, such asmore fully described herein. In FIG. 2, the movable component 228 isillustrated as being a truck. However, it is to be appreciated andunderstood that the movable component 228 can be virtually any desiredmovable component (e.g., motorized vehicle, unmotorized vehicle,motorized device, . . . ) that can be associated with the slicecomponent 202 to move the slice component 202 to desired locations, asmore fully described herein.

Also, as depicted in FIG. 2, the communication device 230 is depicted asbeing associated with entity 236 (e.g., a tractor), the communicationdevice 232 is depicted as being associated with entity 238 (e.g.,another tractor), and the communication device 234 is depicted as beingassociated with entity 240 (e.g., a bulldozer). However, it is to beappreciated and understood that the respective entities (e.g., 236, 238,240) can be different entities from those entities (e.g., tractor, othertractor, bulldozer) depicted in FIG. 2, and the respective entities(e.g., 236, 238, 240) can be virtually any desired type of entity (e.g.,user, vehicle, equipment, or animal, . . . ), such as more fullydescribed herein.

The communication network 204 can comprise an Internet Protocol (IP)multimedia subsystem (IMS) core component 242 (also referred to as an IPmultimedia core network subsystem) that can facilitate providingmultimedia services. When the service slice 216 is generated, theservice slice 216 can comprise or be associated with the IMS corecomponent 242. The IMS core component 242 can be associated with thedatabase component 220 to facilitate providing the services (e.g., 210,or 212, . . . ) and/or data (e.g., service-related data) relating to theservices.

The communication network 204 also can include a common C-planeselection function (CCPSF) 244 that can be associated with or part of acommon plane (CP) function. When the core slice 218 is generated, thecore slice 218 can comprise or be associated with the CCPSF 244. TheCCPSF 244 also can be associated with (e.g., communicatively connectedto) the IMS core component 242. The CCPSF 244 can be employed tofacilitate determining with which common C-plane function that thenetwork node device 206 is to communicate. The CCPSF 244 can determinethe common C-plane function, for example, based at least in part on aprofile (e.g., user or subscription profile) associated with thecommunication device (e.g., 230). If the common C-plane function is tobe changed, the CCPSF 244 (e.g., serving CCPSF) can facilitatedetermining or re-selecting another (e.g., a target) common C-planefunction.

The communication network 204 further can comprise a mobility managementfunction (MM) 246 that can be associated with (e.g., communicativelyconnected to) the CCPSF 244. When the core slice 218 is generated, thecore slice 218 can comprise or be associated with the MM 246. The MM 246can be utilized to facilitate registration of communication devices(e.g., 230, 232, and/or 234) in an operator's network and also canprovide mobility support for communication devices, such as providingmobility function and/or other support when a communication device ismoving between base stations within an operator's communication network.

The communication network 204 also can include an authenticationfunction (AU) 248 (which also can be referred to as an authenticationservice function (AUSF)) that can be associated with (e.g.,communicatively connected to) the MM 246 and/or the CCPSF 244. When thecore slice 218 is generated, the core slice 218 can comprise or beassociated with the AU 248. The AU 248 can be employed to authenticateor authorize (e.g., grant authorization to) a communication device(e.g., 230) to connect or attach to an operator's network. The AU 248also can provide or facilitate providing security and/or integrityservices or protections for non-access stratum (NAS) signaling.

In some embodiments, the communication network 204 can comprise aunified data management (UDM) component 250 that can be associated with(e.g., communicatively connected to) the CCPSF 244 and/or othercomponents of the communication network 102. When the core slice 218 isgenerated, the core slice 218 can comprise or be associated with the UDMcomponent 250. The UDM component 250 can store subscriber data and/orprofiles of subscribers (e.g., users of communication devices). TheCCPSF 244 can access a profile associated with a subscriber tofacilitate determining with which common C-plane function the networknode device 206 is to communicate.

With further regard to the slice component 202, the slice component 202can comprise a sensory unit 252 that can instantiate or facilitateinstantiating the core slice(s) (e.g., internal core slice 218′ and coreslice 218), the service slice(s) (e.g., internal service slice 216′ andservice slice 216), the core functions and capabilities, the VNF 254(also referred to as the service VNF) for the service(s) (e.g., service210, and/or service 212, . . . ), and/or other functions. When the VNF254 is instantiated, the information (e.g., service-related data,software, firmware, . . . ) relating to the service and associatedapplications (e.g., VNF) can be stored in the mobile database component226.

The mobile network device 222 of the slice component 202 can comprisevarious network components (e.g., network node components) or othernetwork components, including, for example, remote radio head (RRH)component 256 (also referred to as remote radio unit or remote radiocomponent), which can be a remote radio transceiver that can connect(e.g., wirelessly and communicatively connect) to the network nodedevice 206 to facilitate connecting to the communication network 204(e.g., connecting the slice component 202 to the communication network204). The RRH component 256 can enable the slice component 202 toconnect and communicate with the communication network 204 when theslice component 202 is located in underserved or unserved areas thatotherwise would not have access to, or would only have limited accessto, the communication network 204, as more fully described herein. TheRRH component 256 also can connect (e.g., wirelessly and communicativelyconnect) to the communication devices (e.g., 230, 232, and/or 234, . . .) that are in a coverage area served by the RRH component 256, which canenable the communication devices to communicate with the slice component202 and access the services (e.g., 210, and/or 212, . . . ) associatedtherewith. The RRH component 256 also can be associated with the sensoryunit 252 to facilitate enabling the sensory unit 252 to instantiate thecore slice(s), the service slice(s), the core functions andcapabilities, the VNF 254 for the service(s), and/or other functions.

The slice component 202 can comprise a baseband unit (BBU) 258 that canbe associated with the sensory unit 252 and RRH component 256. The BBU258 can be part of the mobile core network of the slice component 202.When the internal core slice 218′ is generated, the internal core slice218′ can comprise or be associated with the BBU 258. The BBU 258 can bea baseband processing unit of the slice component 202, and canfacilitate communication and/or managing communication through thephysical interface. The BBU 258 can facilitate modulating data packets(e.g., IP packets) received from the mobile core network of the slicecomponent 202 to generate digital baseband signals that can becommunicated to the RRH component 256. The BBU 258 also can facilitatedemodulating digital baseband signals received from the RRH component256 to obtain the data packets associated with the digital basebandsignals, and can communicate the data packets to the mobile core networkof the slice component 202.

The slice component 202 also can include a mobility management entity(MME) 260 that can be associated with the BBU 258. The MME 260 can bepart of the mobile core network of the slice component 202. When theinternal core slice 218′ is generated, the internal core slice 218′ cancomprise or be associated with the MME 260. The MME 260 can facilitateenabling the control plane to communicate with the mobile core networkof slice component 202. The MME 260 can manage or facilitate managingcommunications with the communication devices (e.g., 230, 232, and/or234, . . . ), including managing access of the communication devices tothe mobile core network of the slice component 202 to gain connectivity(e.g., IP connectivity). The MME 260 also can be employed to initiate orfacilitate performing or managing paging, authentication, and/orauthorization of the communication devices (e.g., 230, 232, and/or 234,. . . ). The MME 260 also can facilitate managing mobility managementfor the communication devices (e.g., 230, 232, and/or 234, . . . ) withregard to network node devices (e.g., 206).

The slice component 202 further can comprise a packet data network (PDN)component 262 that can be associated with the MME 260, the service VNF254, and/or the internal service slice 216′. The PDN component 262 canbe part of the mobile core network of the slice component 202. When theinternal core slice 218′ is generated, the internal core slice 218′ cancomprise or be associated with the PDN component 262. The PDN component262 can facilitate providing data services, and facilitate thecommunication of data using data packets, for the mobile core network ofthe slice component 202. In some embodiments, the PDN component 262 cancomprise a PDN gateway component that can be utilized to act as aninterface between different packet data networks (e.g., mobile corenetwork of the slice component 202 (e.g., mobile core network of an LTEsystem) and an IP-based network or other network).

The slice component 202 also can include a script database component 264that can be associated with (e.g., communicatively connected to) the MME260 and/or other components of the slice component 202. The scriptdatabase component 264 can be part of the mobile core network of theslice component 202. When the internal core slice 218′ is generated, theinternal core slice 218′ can comprise or be associated with the scriptdatabase component 264. The script database component 264 can comprisescripts for one or more services (e.g., service 210, and/or service 212,. . . ) that can be associated with the slice component 202 (e.g., oneor more services with which the slice component 202 can communicate).The slice component 202 (e.g., the MME 260 or other component of theslice component 202) can access the script database component 264 toaccess or obtain a script for a service (e.g., service 210), and cangenerate or facilitate generating the internal service slice 216′ and/orservice slice 216 for the service based at least in part on the scriptfor the service.

FIG. 3 depicts a block diagram of an example, non-limiting slicecomponent 300, in accordance with various aspects and embodiments of thedisclosed subject matter. The slice component 300 can comprise a mobilecore network 302, a mobile network device 304, a mobile service network306, an operations manager component 308, a service slice generatorcomponent 310, a core slice generator component 312, a sensory unit 314,a synchronization component 316 (sync component), a processor component318, and a data store 320.

The mobile core network 302 can comprise various components that can beemployed to facilitate providing core functions and capabilities of themobile core network to facilitate enabling communication devices tocommunicate (e.g., wirelessly communicate) with the slice component 300and enabling the slice component 300 to communicate with other devices(e.g., network node devices of a communication network). The componentsof the mobile core network 302 can comprise routers, nodes, switches,interfaces, controllers, and/or gateways, etc., that can be arranged andconfigured to form the mobile core network 302, and can facilitatecommunication of data between the slice component 300 and thecommunication devices, and/or communication of data between the slicecomponent 300 and network node devices of the communication network. Insome embodiments, the components of the mobile core network 302 cancomprise a BBU, an MME, and/or a PDN. In certain embodiments, one ormore of the various components of the mobile core network 302 can bevirtual components.

In some embodiments, the mobile core network 302 can comprise a scriptdatabase component 322 that can store one or more scripts for one ormore services that can be associated with the slice component 202 and/orcommunication network. The slice component 300 can access the scriptdatabase component 322 to access or obtain a script for a service,wherein the service slice generator component 310 can generate aninternal service slice associated with a service and/or or facilitategenerating (e.g., in coordination with the network slice component) aservice slice associated with the service based at least in part on thescript for the service.

The mobile core network 302 can be associated with (e.g., can becommunicatively connected to or can comprise) a mobile network device304 that can enable the slice component 300 to connect and communicate(e.g., wirelessly connect and communicate) with communication devices inthe coverage area served by the mobile network device 304 and networknode devices associated with the communication network (e.g., macroand/or small cell communication network). In some embodiments, themobile network device 304 can be or can comprise and RRH component thatcan be a remote radio transceiver that can connect (e.g., wirelessly andcommunicatively connect) to a network node device (e.g., base station,eNode, eNodeB, or gNB) of a communication network to facilitateconnecting the slice component 300 to the communication network. Themobile network device 304 (e.g., employing the RRH component) can enablethe slice component 300 to connect and communicate with thecommunication network when the slice component 300 is located inunderserved or unserved areas (e.g., typically underserved or unservedby the communication network), as more fully described herein. Themobile network device 304 also can connect (e.g., wirelessly andcommunicatively connect) to communication devices that are located in acoverage area served by the mobile network device 304, which can enablethe communication devices to communicate with the slice component 300and access the services that can be provided via the slice component300. The mobile network device 304 (e.g., the RRH component of themobile network device 304) also can be associated with the sensory unit314 to facilitate enabling the sensory unit 314 to instantiate coreslices, the service slices, the core functions and capabilities of themobile core network 302, the VNFs for services, and/or other functions.

The mobile service network 306 can comprise various components that canbe employed to facilitate providing one or more services of orassociated with the mobile service network 306. In some embodiments, oneor more of the various components of the mobile service network 306 canbe virtual components. The mobile service network 306 can comprise amobile database component 324 that can be part of or associated with aservice slice generated by the service slice generator component 310,wherein the service slice can be associated with a service that can beprovided by the mobile service network 306 or the service network of thecommunication network (e.g., macro and/or small cell communicationnetwork). The mobile database component 324 can be created, for example,in response to generating the service slice associated with the service.In some embodiments, the mobile database component 324 can be a virtualdatabase. The mobile database component 324 can store information (e.g.,service-related data, software, software updates, firmware, firmwareupdates, VNF-related information, . . . ) relating to the service. Forinstance, the mobile database component 324 can store service-relateddata received from a communication device associated with an entity thatis accessing or utilizing the service. The mobile database component 324also can store service-related data, a software update(s), a firmwareupdate(s), and/or VNF-related information, associated with the servicethat can be received from the service via the service network of thecommunication network. The slice component 300 can retrieve theservice-related data, software update(s), and/or firmware update(s) fromthe mobile database component 324 and can communicate theservice-related data, software update(s), and/or firmware update(s) tothe communication device (or can forward the service-related data,software update(s), and/or firmware update(s) received from thecommunication network to the communication device). The slice component300 also can provide VNFs associated with a service to the communicationdevice based at least in part on the VNF-related information.

The operations manager component 308 can control (e.g., manage)operations associated with the slice component 300. For example, theoperations manager component 308 can facilitate generating instructionsto have components of the slice component 300 perform operations, andcan communicate respective instructions to respective components (e.g.,components of the mobile core network 302, the mobile network device304, components of the mobile service network 306, service slicegenerator component 310, core slice generator component 312, sensoryunit 314, synchronization component 316, processor component 318, datastore 320, . . . ) of the slice component 300 to facilitate performanceof operations by the respective components of the slice component 300based at least in part on the instructions, in accordance with thedefined slice management criteria, the defined security criteria, thedefined slice management algorithm(s), and/or the defined securityalgorithm(s) (e.g., slice management algorithms and/or the definedsecurity algorithms as disclosed, defined, recited, or indicated hereinby the methods, systems, and techniques described herein). Theoperations manager component 308 also can facilitate controlling dataflow between the respective components of the slice component 300 andcontrolling data flow between the slice component 300 and anothercomponent(s) or device(s) (e.g., communication device, base station orother network node component or device of the communication network,communication network, . . . ) associated with (e.g., connected to) theslice component 300.

The service slice generator component 310 can be employed to generate orfacilitate generating service slices associated with services to enablecommunication devices (e.g., communication devices in underserved orunserved areas) in proximity to the slice component 300 to accessdesired services. The service slice generator component 310 can generatean internal service slice associated with a service or facilitategenerating a service slice associated with the service (e.g., at theservice network of the communication network) based at least in part ona script associated with the service (e.g., a script retrieved from thescript database component 322), in accordance with the defined slicemanagement criteria and the defined security criteria relating to theservice.

The core slice generator component 312 can be utilized to generate orfacilitate generating core slices in connection with service slicesassociated with services to facilitate enabling communication devices(e.g., communication devices in underserved or unserved areas) inproximity to the slice component 300 to access desired services. Thecore slice generator component 312 can generate an internal core sliceof the mobile core network or facilitate generating a core slice of thecore network of the communication network, in accordance with thedefined slice management criteria and the defined security criteriarelating to the service being accessed.

The sensory unit 314 can instantiate or facilitate instantiating a coreslice(s) (e.g., internal core slice and/or core slice), a serviceslice(s) (e.g., internal service slice and/or service slice), corefunctions and capabilities, one or more VNFs for a service, and/or otherfunctions. When a VNF is instantiated, the information (e.g.,service-related data, software, firmware, . . . ) relating to theservice and associated applications (e.g., VNF) can be stored in themobile database component 324.

The synchronization component 316 can synchronize information betweenthe slice component 300 and the communication network. With regard to acommunication component accessing or attempting to access a serviceassociated with the communication network, there can be instances wherethe slice component 300 is not able to establish a communicationconnection with the communication network or where a communicationconnection between the slice component 300 and the communication networkis interrupted, lost, or otherwise discontinued. In such instances, theslice component 300 is able to provide the communication device all or aportion of the service and associated applications, functions,resources, etc., even though the slice component 300 is not connected tothe communication network and associated service network, as more fullydescribed herein. While not connected to the communication network, theslice component 300 can employ the service slice generator component 310to generate an internal slice for the service, and the core slicegenerator component 312 can generate a corresponding internal core slicein connection with the service to facilitate providing all or a portionof the service, creating a secure communication channel between theslice component 300 and communication device with regard to providingall or a portion of the service, communicating information in connectionwith the service between the slice component 300 and communicationdevice, etc., as more fully described herein. For instance, during thecommunication session, the slice component 300 can obtain information(e.g., service-related data) from the communication device and/or canprovide all or at least a portion of the service (e.g., functions,applications, VNFs, service-related data, . . . ) to the communicationdevice.

With regard to the communication session (or portion of thecommunication session) that was occurring while the slice component 300(and communication device) was not connected to the communicationnetwork, in response to establishing or re-establishing thecommunication connection and secure communication channel with thecommunication network, the synchronization component 316, employing themobile network device 304 and a secure communication channel, canfacilitate communicating information relating to the communicationsession (or portion thereof) associated with the communication device(to the service network associated with the communication network,and/or receiving other information from the service network for storagein the mobile service network 306 (e.g., mobile database component 324or other data store) for communication to the communication device, tosynchronize information between the service network (e.g., the databasecomponent of the service network) and the mobile service network 306(e.g., the mobile database component 324 of the mobile service network306) and/or to provide the other information, or a portion thereof, tothe communication device in connection with the communication session.

The processor component 318 can work in conjunction with the othercomponents (e.g., mobile core network 302, mobile network device 304,mobile service network 306, operations manager component 308, serviceslice generator component 310, core slice generator component 312,sensory unit 314, synchronization component 316, and/or data store 320,. . . ) to facilitate performing the various functions of the slicecomponent 300. The processor component 318 can employ one or moreprocessors, microprocessors, or controllers that can process data, suchas information relating to communication devices (e.g., UEs), parametersrelating to data communications, communication sessions, signaling,services, service slices, core slices, applications, VNFs, defined slicemanagement criteria, defined security criteria, traffic flows, policies,algorithms (e.g., slice management algorithm(s), securityalgorithm(s),), protocols, interfaces, tools, and/or other information,to facilitate operation of the slice component 300, as more fullydisclosed herein, and control data flow between the slice component 300and other components (e.g., mobile devices (e.g., communication device),other network devices (e.g., network node devices) of the communicationnetwork, data sources, applications, . . . ) associated with the slicecomponent 300.

The data store 320 can store data structures (e.g., user data,metadata), code structure(s) (e.g., modules, objects, hashes, classes,procedures) or instructions, information relating to communicationdevices (e.g., UEs), parameters relating to data communications,communication sessions, signaling, services, service slices, coreslices, applications, VNFs, defined slice management criteria, definedsecurity criteria, traffic flows, policies, algorithms (e.g., slicemanagement algorithm(s), security algorithm(s),), protocols, interfaces,tools, and/or other information, to facilitate controlling operationsassociated with the slice component 300. In an aspect, the processorcomponent 318 can be functionally coupled (e.g., through a memory bus)to the data store 320 in order to store and retrieve information desiredto operate and/or confer functionality, at least in part, to the mobilecore network 302, mobile network device 304, mobile service network 306,operations manager component 308, service slice generator component 310,core slice generator component 312, sensory unit 314, synchronizationcomponent 316, and/or data store 320, etc., and/or substantially anyother operational aspects of the slice component 300.

It should be appreciated that the data store 320 described herein cancomprise volatile memory and/or nonvolatile memory. By way of exampleand not limitation, nonvolatile memory can include read only memory(ROM), programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which can act as external cachememory. By way of example and not limitation, RAM can be available inmany forms such as synchronous RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhancedSDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Memory of the disclosed aspects are intended to comprise, without beinglimited to, these and other suitable types of memory.

The systems and/or devices have been (or will be) described herein withrespect to interaction between several components. It should beappreciated that such systems and components can include thosecomponents or sub-components specified therein, some of the specifiedcomponents or sub-components, and/or additional components.Sub-components could also be implemented as components communicativelycoupled to other components rather than included within parentcomponents. Further yet, one or more components and/or sub-componentsmay be combined into a single component providing aggregatefunctionality. The components may also interact with one or more othercomponents not specifically described herein for the sake of brevity,but known by those of skill in the art.

In view of the example systems and/or devices described herein, examplemethods that can be implemented in accordance with the disclosed subjectmatter can be further appreciated with reference to flowchart in FIGS.4-6. For purposes of simplicity of explanation, example methodsdisclosed herein are presented and described as a series of acts;however, it is to be understood and appreciated that the disclosedsubject matter is not limited by the order of acts, as some acts mayoccur in different orders and/or concurrently with other acts from thatshown and described herein. For example, a method disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a method inaccordance with the subject specification. It should be furtherappreciated that the methods disclosed throughout the subjectspecification are capable of being stored on an article of manufactureto facilitate transporting and transferring such methods to computersfor execution by a processor or for storage in a memory.

FIG. 4 illustrates a flow diagram of an example, non-limiting method 400that can generate and manage a slice of a service network for acommunication device, in accordance with various aspects and embodimentsof the disclosed subject matter. The method 400 can be implemented by aslice component that can comprise or be associated with a processor amemory. Alternatively, or additionally, a machine-readable storagemedium can comprise executable instructions that, when executed by aprocessor, facilitate performance of operations for the method 400.

At 402, a wireless communication connection can be established between acommunication device, for example, in an underserved/unserved area, anda communication network via a mobile network device (e.g., mobilenetwork node device, movable network device) located in proximity to thecommunication device. The communication device can be located, forexample, in an underserved/unserved area (e.g., rural or pastoral area)where typically there can be limited or no wireless communicationcoverage available to provide wireless communication services tocommunication devices, such as the communication device, to enableconnection to the communication network (e.g., macro and/or small cellcommunication network), and/or no or inadequate advance capabilities(e.g., network slicing). The slice component can be associated with avehicle or movable device (e.g., motorized device that can move to adesired location), and the slice component can comprise or be associatedwith a mobile (e.g., local, internal) communication network comprisingmobile network devices, wherein the slice component and the mobilecommunication network can move with the vehicle or movable device. Thevehicle or movable device can move to be located in proximity to (e.g.,within a defined distance of) the communication device to enable thewireless communication connection to be established between thecommunication device and a network device of the communication networkvia the mobile network device and a network node device (e.g., basestation, eNode, eNodeB, or gNB) of or associated with the communicationnetwork. For instance, the slice component can initiate, establish, orfacilitate establishing the wireless communication connection betweenthe communication device and the communication network via the mobilenetwork device of the mobile communication network when the vehicle ormovable (e.g., motorized) device, and the associated slice component andmobile communication network, are located (e.g., travel to be located)in proximity to the communication device.

At 404, a slice of a service network can be generated (e.g., created)for a communication device to facilitate secure communication ofinformation between the service network and the communication deviceusing the slice (and associated wireless communication connection). Theslice component can generate or facilitate generating the slice (e.g.,service slice) of the service network, and a corresponding slice (e.g.,core slice) of the core network of the communication network, for use bythe communication device. The slice of the service network, inconjunction with the corresponding slice of the core network, can enableproviding a secure communication channel between the service network andthe communication device, providing applications and functions (e.g.,VNFs) to the communication device, and secure communication ofinformation between the service network (of or associated with thecommunication network) and the communication device using the slice ofthe service network (and associated wireless communication connectionprovided via the mobile network device).

FIG. 5 depicts a flow diagram of another example, non-limiting method500 that can generate and manage a slice of a service network for acommunication device, in accordance with various aspects and embodimentsof the disclosed subject matter. The method 500 can be implemented by aslice component that can comprise or be associated with a processor amemory. Alternatively, or additionally, a machine-readable storagemedium can comprise executable instructions that, when executed by aprocessor, facilitate performance of operations for the method 500.

At 502, to facilitate establishing a communication session, acommunication connection (e.g., wireless communication connection) canbe established between a communication device, for example, located inan underserved/unserved area, and a network device of a communicationnetwork via a mobile network device located in proximity to thecommunication device. The communication device can be located, forexample, in an underserved/unserved area (e.g., rural or pastoral area)where often there can be limited or no wireless communication coverageavailable to provide wireless communication services to communicationdevices, such as the communication device, to enable connection to anetwork device (e.g., macro or small cell communication network device)of the communication network (e.g., macro or small cell communicationnetwork), and/or no or inadequate advance capabilities (e.g., networkslicing). The slice component can be associated with a movable component(e.g., a vehicle (e.g., a motorized, or unmotorized or manually operatedvehicle), or a motorized device), and the slice component can be or cancomprise the mobile network device. The slice component can initiate,establish, or facilitate establishing (e.g., generating) thecommunication connection between the communication device and thenetwork device of the communication network via the mobile networkdevice, for example, when the vehicle and associated slice component arelocated (e.g., travel to be located) in proximity to the communicationdevice.

At 504, a slice of the service network can be generated for thecommunication device. The slice component can generate or facilitategenerating the slice (e.g., service slice) of the service network,wherein the slice can be part of the service network associated with thecommunication network, and wherein the slice can relate to a serviceprovided by the service network. The slice component can comprise, beassociated with, and/or manage a mobile (e.g., local, internal) servicenetwork, wherein the mobile service network can comprise all or adesired portion of the applications and functionality (e.g., VNFs),scripts (e.g., code and other data for applications), data (e.g., datastored in the database component), etc., of the service networkassociated with the communication network. The slice component cancoordinate with the network slice component of the communication networkto facilitate generating the slice of the service network. The slicecomponent also can coordinate with the network slice component tofacilitate generating a core slice of the core network of thecommunication network. The slice component, employing the mobile networkdevice, also can coordinate with the communication network to facilitategenerating the core slice of the core network of the communicationnetwork.

As part of generating the slice and establishing the communicationconnection, the slice component can create a secure communicationchannel between the communication device and the service network (e.g.,a service network device of the service network) via the mobile networkdevice, wherein the secure communication channel can be used to securelycommunicate information between the communication device and the servicenetwork via the mobile network device. The secure communication channelcan enable secure communication of information between the communicationdevice and the service network via the mobile network device, inaccordance with defined security criteria (e.g., as applicable, securitycriteria relating to HIPAA compliance, security criteria relating tomilitary communications, security criteria relating to law enforcementcommunications, . . . ).

At 506, all or a desired portion of applications, functionality, and/orinformation associated with the service network can be provided orcommunicated to the communication device by the service network (ormobile service network) via the mobile network device. The slicecomponent, employing the service slice (and corresponding core slice),the mobile service network, and the secure communication channel, canprovide (e.g., make available), facilitate providing, communicate, orfacilitate communicating, all or a desired portion of the applications,functionality, and/or information (e.g., service-related data, softwareor firmware updates, . . . ) associated with the service network (e.g.,for the desired service of the service network) to the communicationdevice, via the secure communication channel, to facilitate enabling thecommunication device to utilize the desired service associated with theslice in a secure environment. For instance, the slice component canprovide, or facilitate providing, desired VNFs and/or information fromthe service network (or mobile service network) to the communicationdevice, via the secure communication channel.

At 508, other information (e.g., data obtained by the communicationdevice or associated sensors or other components, and/or other dataobtained by the communication device from another communicationdevice(s) associated therewith) can be communicated from thecommunication device to the service network (e.g., a service networkdevice of the service network) using the slice of the service network(and corresponding core slice). The slice component, by providing andmanaging the service slice (and corresponding core slice), canfacilitate enabling such other information to be communicated from thecommunication device to the service network using the service slice ofthe service network (and the corresponding core slice). For example,using the service slice, the service network can receive and collectinformation from the communication device, wherein such information canbe stored in the database component of the service network. In someembodiments, such other information can comprise information obtainedfrom one or more other communication devices by the communicationdevice, in addition to information that the communication devicecollected itself (e.g., with respect to the entity with which it isassociated, and/or conditions or characteristics associated with theentity and/or communication device, . . . ).

For example, the respective communication devices can comprise or beassociated with respective sensors or other components that can sense oridentify respective conditions, characteristics, measurements, etc.,associated with the respective communication devices and/or respectivelyassociated entities. The communication device can receive the respectiveinformation (e.g., information obtained by the respective sensors orother components) from the other communication devices. Thecommunication device can communicate the information it obtained fromits sensors or other components, and the other information it receivedfrom the other communication devices, to the service network, via asecure communication channel, using the slice of the service network(and corresponding core slice).

FIG. 6 illustrates a flow diagram of an example, non-limiting method 600that, for a communication device, can generate and manage an internalslice of a local service network associated with a local (e.g., mobile)communication network associated with a vehicle or movable device, andsynchronize information between the local service network and a servicenetwork of a communication network, in accordance with various aspectsand embodiments of the disclosed subject matter. The method 600 can beimplemented by a slice component that can comprise or be associated witha processor a memory. Alternatively, or additionally, a machine-readablestorage medium can comprise executable instructions that, when executedby a processor, facilitate performance of operations for the method 600.

At 602, a determination can be made that a mobile network deviceassociated with a movable component (e.g., vehicle or motorized device)is unable to establish or maintain a communication connection with acommunication network and associated service network. The slicecomponent of or associated with the movable component can be, cancomprise, or be associated with the mobile network device, which can beused to establish a communication connection (e.g., wirelesscommunication connection) between the communication network (e.g., macroor small cell communication network) (and associated service network)and a communication device located in an area where the movablecomponent is located. The area can be an underserved or unserved areawhere wireless communication coverage of the communication networktypically can be limited or non-existent.

In some instances (e.g., due to interference between mobile networkdevice and the communication network), it may not be possible toestablish a communication connection, or to maintain a communicationconnection, between the mobile network device and the communicationnetwork. In such instances, the slice component can determine that themobile network device associated with the movable component is unable toestablish or maintain a communication connection with the communicationnetwork and associated service network.

At 604, to facilitate establishing a communication session, acommunication connection (e.g., wireless communication connection) canbe established between the communication device in theunderserved/unserved area and the mobile network device located inproximity to the communication device. The slice component, employingthe mobile network device of the mobile (e.g., local, internal) corenetwork of, associated with, and/or managed by the slice component, canestablish the communication connection, including a secure communicationchannel (e.g., as part of generating an internal slice, as describedwith regard to reference numeral 606), between the communication deviceand the mobile network device. The secure communication channel canenable secure communication of information between the communicationdevice and the mobile network device, in accordance with definedsecurity criteria (e.g., security criteria, as applicable, relating toHIPAA compliance, security criteria relating to military communications,security criteria relating to law enforcement communications, . . . ).

At 606, an internal slice of the service network can be generated forthe communication device. The slice component can generate an internalslice (e.g. internal service slice) associated with the service network,wherein the internal slice can be part of the mobile (e.g., local,internal, portable) service network associated with the mobile networkdevice. The slice component also can generate or facilitate generating acorresponding internal core slice of a mobile core network associatedwith the mobile network device.

The slice component also can comprise, be associated with, and/or managethe mobile service network, wherein the mobile service network cancomprise all or a desired portion of the applications and functionality(e.g., VNFs), scripts (e.g., code and other data for applications), data(e.g., service-related data stored in the database component), etc., ofthe service network associated with the communication network. As partof generating the internal slice (and corresponding internal core slice)and establishing the communication connection, the slice component cancreate a secure communication channel that can be used to securelycommunicate information between the communication device and the mobileservice network via the mobile network device associated with the mobilecore network.

At 608, employing the internal slice, all or a portion of applications,functionality, and data associated with the service network can beprovided to the communication device via the mobile (e.g., internal,local, portable) service network associated with the mobile networkdevice. The slice component, employing the internal slice (and internalcore slice) and the mobile service network, can provide all or a portionof the applications, functionality, and data associated with the servicenetwork to the communication device to facilitate enabling thecommunication device to utilize the desired service associated with theinternal slice in a secure environment.

At 610, information can be communicated from the communication device tothe mobile service network using the internal slice. At 612, suchinformation can be stored in a mobile database component of the mobileservice network associated with the internal slice. During thecommunication session, information can be received, via the securecommunication channel, from the communication device by the mobileservice network and stored in the mobile database component of themobile service network associated with the slice component and mobilenetwork device. Additionally or alternatively, other information storedin the mobile database component (e.g., information relating to theservice and/or the user, entity, or equipment, etc., associated with thecommunication device) can be communicated, via the secure communicationchannel, from the mobile service network to the communication device(e.g., as indicated at reference numeral 608).

At 614, a communication connection (e.g., a wireless communicationconnection) can be established between the mobile network device and thecommunication network and associated service network (and/oraccordingly, via the mobile network device, between the communicationdevice and the communication network and associated service network).The slice component, employing the mobile network device, can determinethat a communication connection can be established between the mobilenetwork device and the communication network and associated servicenetwork. For example, a movable component (e.g., a vehicle, or motorizedor movable device) associated with the slice component can move to alocation where the mobile network device is able to connect to thecommunication network (e.g., macro or small cell communication network)and/or interference that was inhibiting connection between the mobilenetwork device and the communication network can be mitigated or removed(e.g., whether or not the vehicle moves to a different location). Inresponse to determining that a communication connection can beestablished between the mobile network device and the communicationnetwork, the slice component can establish the communication connection(e.g., wireless communication connection), including a securecommunication channel, between the mobile network device and thecommunication network and associated service network (and/or between thecommunication device and the communication network and associatedservice network (e.g., if the communication session of the communicationdevice is still in progress)).

At 616, a slice of the service network can be generated with respect tothe communication device. The slice component can generate the slice(e.g., service slice) of the service network associated with thecommunication network and/or a corresponding slice (e.g., core slice) ofthe core network of the communication network. As part of generating theslice (and/or the corresponding slice of the core network) andestablishing the communication connection with the communicationnetwork, the slice component can create a secure communication channelthat can be used to securely communicate information between the mobilenetwork device and the service network (and/or between the communicationdevice and the service network via the mobile network device (e.g., ifthe communication session with the communication device is still inprogress)).

The network slice component of the communication network can coordinatewith the slice component associated with the movable component tofacilitate generation of the slice of the service network (and/orcorresponding slice of the core network). The network slice componentcan comprise, be associated with, and/or manage the service network,wherein the service network can comprise the applications andfunctionality (e.g., VNFs), scripts (e.g., code and other data forapplications), information (e.g., information stored in the databasecomponent), etc., of the service network.

At 618, in response to establishing the communication connection and theslice between the mobile network device and the communication network(and associated service network), information relating to thecommunication session can be synchronized between the service networkand the mobile service network. The slice component, employing themobile network device and the secure communication channel, canfacilitate communicating information relating to the communicationsession associated with the communication device to the service network,and/or receiving other information from the service network forcommunication to the communication device, to synchronize informationbetween the service network (e.g., the database component of the servicenetwork) and the mobile service network (e.g., the mobile databasecomponent of the mobile service network) and/or to provide the otherinformation, or a portion thereof, to the communication device inconnection with the communication session. For instance, the otherinformation can be determined (e.g., by the network slice component)based at least in part on (e.g., in response to) the informationrelating to the communication session communicated to the servicenetwork. If the communication session, which had been using the internalslice, is still in progress, the communication session can continueusing the slice (e.g., service slice) and corresponding slice (e.g.,core slice).

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate generating(e.g., creating) slices of a service network (e.g., inunderserved/unserved geographical areas, such as rural areas, using amobile (e.g., movable) network device), generating slices of a corenetwork, securely communicating information via a secure communicationchannel using the slices, providing applications and functionsassociated with services, securely performing software and firmwareupdates using the secure slices, and performing other functions andoperations, as more fully described herein. Facilitating generatingslices of a service network, generating slices of a core network,securely communicating information via a secure communication channelusing the slices, providing applications and functions associated withservices, securely performing software and firmware updates using thesecure slices, and performing other functions and operations can beimplemented in connection with any type of device with a connection tothe communications network (e.g., a mobile device, a computer, ahandheld device, a wearable device, etc.) any Internet of things (IoT)device (e.g., toaster, coffee maker, blinds, music players, speakers,etc.), and/or any connected vehicles (cars, airplanes, space rockets,and/or other at least partially automated vehicles (e.g., drones)). Insome embodiments, the non-limiting term User Equipment (UE) is used. Itcan refer to any type of wireless device that communicates with a radionetwork node in a cellular or mobile communication system. Examples ofUE are target device, device to device (D2D) UE, machine type UE or UEcapable of machine to machine (M2M) communication, PDA, Tablet, mobileterminals, smart phone, Laptop Embedded Equipped (LEE), laptop mountedequipment (LME), USB dongles etc. Note that the terms element, elementsand antenna ports can be interchangeably used but carry the same meaningin this disclosure. The embodiments are applicable to single carrier aswell as to Multi-Carrier (MC) or Carrier Aggregation (CA) operation ofthe UE. The term Carrier Aggregation (CA) is also called (e.g.,interchangeably called) “multi-carrier system,” “multi-cell operation,”“multi-carrier operation,” “multi-carrier” transmission and/orreception.

In some embodiments, the non-limiting term radio network node or simplynetwork node is used. It can refer to any type of network node thatserves one or more UEs and/or that is coupled to other network nodes ornetwork elements or any radio node from where the one or more UEsreceive a signal. Examples of radio network nodes are Node B, BaseStation (BS), Multi-Standard Radio (MSR) node such as MSR BS, eNode B,network controller, Radio Network Controller (RNC), Base StationController (BSC), relay, donor node controlling relay, Base TransceiverStation (BTS), Access Point (AP), transmission points, transmissionnodes, RRU, RRH, nodes in Distributed Antenna System (DAS) etc.

Cloud Radio Access Networks (RAN) can enable the implementation ofconcepts such as Software-Defined Network (SDN) and Network FunctionVirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openApplication Programming Interfaces (APIs) and move the network coretowards an all Internet Protocol (IP), cloud based, and software driventelecommunications network. The SDN controller can work with, or takethe place of Policy and Charging Rules Function (PCRF) network elementsso that policies such as quality of service and traffic management androuting can be synchronized and managed end to end.

To meet the huge demand for data centric applications, 4G standards canbe applied to 5G, also called New Radio (NR) access. 5G networks cancomprise the following: data rates of several tens of megabits persecond supported for tens of thousands of users; 1 gigabit per secondcan be offered simultaneously (or concurrently) to tens of workers onthe same office floor; several hundreds of thousands of simultaneous (orconcurrent) connections can be supported for massive sensor deployments;spectral efficiency can be enhanced compared to 4G; improved coverage;enhanced signaling efficiency; and reduced latency compared to LTE. Inmulticarrier system such as OFDM, each subcarrier can occupy bandwidth(e.g., subcarrier spacing). If the carriers use the same bandwidthspacing, then it can be considered a single numerology. However, if thecarriers occupy different bandwidth and/or spacing, then it can beconsidered a multiple numerology.

Referring now to FIG. 7, depicted is an example block diagram of anexample mobile device 700 (e.g., mobile communication device, mobilehandset) operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein. Although a mobile device is illustrated herein, it will beunderstood that other devices can be a mobile device, and that themobile device is merely illustrated to provide context for theembodiments of the various embodiments described herein. The followingdiscussion is intended to provide a brief, general description of anexample of a suitable environment in which the various embodiments canbe implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the disclosedsubject matter also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, solid statedrive (SSD) or other solid-state storage technology, Compact Disk ReadOnly Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer. In this regard, the terms “tangible” or “non-transitory”herein as applied to storage, memory or computer-readable media, are tobe understood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The device 700 can include a processor 702 for controlling andprocessing all onboard operations and functions. A memory 704 interfacesto the processor 702 for storage of data and one or more applications706 (e.g., a video player software, user feedback component software,etc.). Other applications can include voice recognition of predeterminedvoice commands that facilitate initiation of the user feedback signals.The applications 706 can be stored in the memory 704 and/or in afirmware 708, and executed by the processor 702 from either or both thememory 704 or/and the firmware 708. The firmware 708 can also storestartup code for execution in initializing the device 700. Acommunication component 710 can interface to the processor 702 tofacilitate wired/wireless communication with external systems, e.g.,cellular networks, VoIP networks, and so on. Here, the communicationcomponent 710 also can include a suitable cellular transceiver 711(e.g., a GSM transceiver) and/or an unlicensed transceiver 713 (e.g.,Wi-Fi, WiMax) for corresponding signal communications. The device 700can be a device such as a cellular telephone, a PDA with mobilecommunications capabilities, and messaging-centric devices. Thecommunication component 710 also facilitates communications receptionfrom terrestrial radio networks (e.g., broadcast), digital satelliteradio networks, and Internet-based radio services networks.

The device 700 includes a display 712 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 712 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 712 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface714 is provided in communication with the processor 702 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the device 700, for example. Audio capabilities areprovided with an audio I/O component 716, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 716 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The device 700 can include a slot interface 718 for accommodating a SIC(Subscriber Identity Component) in the form factor of a card SubscriberIdentity Module (SIM) or universal SIM 720, and interfacing the SIM card720 with the processor 702. However, it is to be appreciated that theSIM card 720 can be manufactured into the device 700, and updated bydownloading data and software.

The device 700 can process IP data traffic through the communicationcomponent 710 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the device 700 and IP-based multimediacontent can be received in either an encoded or a decoded format.

A video processing component 722 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 722can aid in facilitating the generation, editing, and sharing of videoquotes. The device 700 also includes a power source 724 in the form ofbatteries and/or an AC power subsystem, which power source 724 caninterface to an external power system or charging equipment (not shown)by a power I/O component 726.

The device 700 can also include a video component 730 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 730 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 732 facilitates geographically locating the device 700. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 734facilitates the user initiating the quality feedback signal. The userinput component 734 can also facilitate the generation, editing andsharing of video quotes. The user input component 734 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 706, a hysteresis component 736 canfacilitate the analysis and processing of hysteresis data, which can beutilized to determine when to associate with the access point. Asoftware trigger component 738 can be provided that facilitatestriggering of the hysteresis component 736 when the Wi-Fi transceiver713 detects the beacon of the access point. A SIP client 740 enables thedevice 700 to support SIP protocols and register the subscriber with theSIP registrar server. The applications 706 can also include a client 742that provides at least the capability of discovery, play and store ofmultimedia content, for example, music.

The device 700, as indicated above related to the communicationcomponent 710, includes an indoor network radio transceiver 713 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM device (e.g., device 700). Thedevice 700 can accommodate at least satellite radio services through adevice that can combine wireless voice and digital radio chipsets into asingle handheld device.

FIG. 8 illustrates a block diagram of an example AP 800 (e.g., a mobilenetwork device or mobile AP, macro base station, eNode, eNodeB, gNB,femto AP, pico AP, Wi-Fi AP, Wi-Fi-direct AP, . . . ), in accordancewith various aspects and embodiments of the disclosed subject matter.For example, the AP 800 can be, or can be associated with, a mobilenetwork device that can be associated with a mobile communicationnetwork and associated mobile service network (associated with a servicenetwork that can be associated with the communication network), whereinthe AP 800 can be associated with (e.g., part of, attached to, orintegrated with a movable component, such as a vehicle or movabledevice). The AP 800 can receive and transmit signal(s) from and towireless devices like access points (e.g., base stations, femtocells,picocells,), access terminals (e.g., UEs), wireless ports and routers,and the like, through a set of antennas 869 ₁-869 _(R). In an aspect,the antennas 869 ₁-869 _(R) are a part of a communication platform 802,which comprises electronic components and associated circuitry that canprovide for processing and manipulation of received signal(s) andsignal(s) to be transmitted. In an aspect, the communication platform802 can include a receiver/transmitter 804 that can convert signal fromanalog to digital upon reception, and from digital to analog upontransmission. In addition, receiver/transmitter 804 can divide a singledata stream into multiple, parallel data streams, or perform thereciprocal operation.

In an aspect, coupled to receiver/transmitter 804 can be amultiplexer/demultiplexer (mux/demux) 806 that can facilitatemanipulation of signal in time and frequency space. The mux/demux 806can multiplex information (e.g., data/traffic and control/signaling)according to various multiplexing schemes such as, for example, timedivision multiplexing (TDM), frequency division multiplexing (FDM),orthogonal frequency division multiplexing (OFDM), code divisionmultiplexing (CDM), space division multiplexing (SDM), etc. In addition,mux/demux component 806 can scramble and spread information (e.g.,codes) according to substantially any code known in the art, e.g.,Hadamard-Walsh codes, Baker codes, Kasami codes, polyphase codes, and soon. A modulator/demodulator (mod/demod) 808 also can be part of thecommunication platform 802, and can modulate information according tomultiple modulation techniques, such as frequency modulation, amplitudemodulation (e.g., M-ary quadrature amplitude modulation (QAM), with M apositive integer), phase-shift keying (PSK), and the like.

The AP 800 also can comprise a processor(s) 810 that can be configuredto confer and/or facilitate providing functionality, at least partially,to substantially any electronic component in or associated with the AP800. For instance, the processor(s) 810 can facilitate operations ondata (e.g., symbols, bits, or chips) for multiplexing/demultiplexing,modulation/demodulation, such as effecting direct and inverse fastFourier transforms, selection of modulation rates, selection of datapacket formats, inter-packet times, etc.

In another aspect, the AP 800 can include a data store 812 that canstore data structures; code instructions; rate coding information;information relating to measurement of radio link quality or receptionof information related thereto; information relating to communicationdevices (e.g., UEs), control channels, control channel formats, controlchannel information, CSI, parameters relating to data communications,reference signals, signaling, reference signal management criteria,traffic flows, policies, algorithms (e.g., algorithms relating tomultiplexing/demultiplexing or modulation/demodulation); white listinformation, information relating to managing or maintaining the whitelist; system or device information like policies and specifications;code sequences for scrambling; spreading and pilot transmission; floorplan configuration; access point deployment and frequency plans;scheduling policies; and so on. The processor(s) 810 can be coupled tothe data store 812 in order to store and retrieve information (e.g.,information, such as algorithms relating to multiplexing/demultiplexingor modulation/demodulation; information relating to radio link levels;information relating to establishing communication connectionsassociated with a communication device(s) served by the AP 800; . . . )desired to operate and/or confer functionality to the communicationplatform 802 and/or other operational components of AP 800.

Referring now to FIG. 9, illustrated is an example block diagram of anexample computer 900 operable to engage in a system architecture thatfacilitates wireless communications according to one or more embodimentsdescribed herein. The computer 900 can provide networking andcommunication capabilities between a wired or wireless communicationnetwork and a server (e.g., Microsoft server) and/or communicationdevice. In order to provide additional context for various aspectsthereof, FIG. 9 and the following discussion are intended to provide abrief, general description of a suitable computing environment in whichthe various aspects of the disclosed subject matter can be implementedto facilitate generating and managing slices (e.g., service slices,internal service slices, core slices, internal core slices) associatedwith services, providing and managing services and service-relatedfunctions and applications, communicating (e.g., securely communicating)information associated with services, in or associated with acommunication network and/or a mobile network (e.g., mobile servicenetwork, mobile core network) in underserved or unserved areas, as morefully described herein. While the description above is in the generalcontext of computer-executable instructions that can run on one or morecomputers, those skilled in the art will recognize that the disclosedsubject also can be implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the disclosed subject matter can also bepracticed in distributed computing environments where certain tasks areperformed by remote processing devices that can be linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules, or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 9, implementing various aspects described hereinwith regards to the end-user device can include a computer 900, thecomputer 900 including a processing unit 904, a system memory 906 and asystem bus 908. The system bus 908 couples system components including,but not limited to, the system memory 906 to the processing unit 904.The processing unit 904 can be any of various commercially availableprocessors. Dual microprocessors and other multi processor architecturescan also be employed as the processing unit 904.

The system bus 908 can be any of several types of bus structure that canfurther interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 906 includesread-only memory (ROM) 927 and random access memory (RAM) 912. A basicinput/output system (BIOS) is stored in a non-volatile memory 927 suchas ROM, EPROM, EEPROM, which BIOS contains the basic routines that helpto transfer information between elements within the computer 900, suchas during start-up. The RAM 912 can also include a high-speed RAM suchas static RAM for caching data.

The computer 900 further includes an internal hard disk drive (HDD) 914(e.g., EIDE, SATA), which internal hard disk drive 914 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 916, (e.g., to read from or write to aremovable diskette 918) and an optical disk drive 920, (e.g., reading aCD-ROM disk 922 or, to read from or write to other high capacity opticalmedia such as the DVD). The hard disk drive 914, magnetic disk drive 916and optical disk drive 920 can be connected to the system bus 908 by ahard disk drive interface 924, a magnetic disk drive interface 926 andan optical drive interface 928, respectively. The interface 924 forexternal drive implementations includes at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of thedisclosed subject matter.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 900 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 900, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the exemplary operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed subject matter.

A number of program modules can be stored in the drives and RAM 912,including an operating system 930, one or more application programs 932,other program modules 934 and program data 936. All or portions of theoperating system, applications, modules, and/or data can also be cachedin the RAM 912. It is to be appreciated that the disclosed subjectmatter can be implemented with various commercially available operatingsystems or combinations of operating systems.

A user can enter commands and information into the computer 900 throughone or more wired/wireless input devices, e.g., a keyboard 938 and apointing device, such as a mouse 940. Other input devices (not shown)can include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 904 through an input deviceinterface 942 that is coupled to the system bus 908, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 944 or other type of display device is also connected to thesystem bus 908 through an interface, such as a video adapter 946. Inaddition to the monitor 944, a computer 900 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 900 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 948. The remotecomputer(s) 948 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 950 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 952 and/or larger networks,e.g., a wide area network (WAN) 954. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which canconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 900 is connectedto the local network 952 through a wired and/or wireless communicationnetwork interface or adapter 956. The adapter 956 can facilitate wiredor wireless communication to the LAN 952, which can also include awireless access point disposed thereon for communicating with thewireless adapter 956.

When used in a WAN networking environment, the computer 900 can includea modem 958, or is connected to a communications server on the WAN 954,or has other means for establishing communications over the WAN 954,such as by way of the Internet. The modem 958, which can be internal orexternal and a wired or wireless device, is connected to the system bus908 through the input device interface 942. In a networked environment,program modules depicted relative to the computer, or portions thereof,can be stored in the remote memory/storage device 950. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers can beused.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi, Bluetooth™, andnear field communication (NFC) wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, in a hotel room, or a conference room at work, withoutwires. Wi-Fi is a wireless technology similar to that used in a cellphone that enables such devices, e.g., computers, to send and receivedata indoors and out; anywhere within the range of a base station. Wi-Finetworks use radio technologies called IEEE 802.11 (a, b, g, etc.) toprovide secure, reliable, fast wireless connectivity. A Wi-Fi networkcan be used to connect computers to each other, to the Internet, and towired networks (which use IEEE 802.3 or Ethernet). Wi-Fi networksoperate in the unlicensed 2.4 and 5 GHz radio bands, at an 11 Mbps(802.11a) or 54 Mbps (802.11b) data rate, for example, or with productsthat contain both bands (dual band), so the networks can providereal-world performance similar to the basic 10BaseT wired Ethernetnetworks used in many offices.

An aspect of 5G, which differentiates from previous 4G systems, is theuse of NR. NR architecture can be designed to support multipledeployment cases for independent configuration of resources used forRACH procedures. Since the NR can provide additional services than thoseprovided by LTE, efficiencies can be generated by leveraging the prosand cons of LTE and NR to facilitate the interplay between LTE and NR,as discussed herein.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics can be combined in any suitable manner in one or moreembodiments.

As used in this disclosure, in some embodiments, the terms “component,”“system,” “interface,” and the like can refer to, or comprise, acomputer-related entity or an entity related to an operational apparatuswith one or more specific functionalities, wherein the entity can beeither hardware, a combination of hardware and software, software, orsoftware in execution, and/or firmware. As an example, a component canbe, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution,computer-executable instructions, a program, and/or a computer. By wayof illustration and not limitation, both an application running on aserver and the server can be a component.

One or more components can reside within a process and/or thread ofexecution and a component can be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components can communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software application orfirmware application executed by one or more processors, wherein theprocessor can be internal or external to the apparatus and can executeat least a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can comprise a processor therein to executesoftware or firmware that confer(s) at least in part the functionalityof the electronic components. In an aspect, a component can emulate anelectronic component via a virtual machine, e.g., within a cloudcomputing system. While various components have been illustrated asseparate components, it will be appreciated that multiple components canbe implemented as a single component, or a single component can beimplemented as multiple components, without departing from exampleembodiments.

In addition, the words “example” and “exemplary” are used herein to meanserving as an instance or illustration. Any embodiment or designdescribed herein as “example” or “exemplary” is not necessarily to beconstrued as preferred or advantageous over other embodiments ordesigns. Rather, use of the word example or exemplary is intended topresent concepts in a concrete fashion. As used in this application, theterm “or” is intended to mean an inclusive “or” rather than an exclusive“or.” That is, unless specified otherwise or clear from context, “Xemploys A or B” is intended to mean any of the natural inclusivepermutations. That is, if X employs A; X employs B; or X employs both Aand B, then “X employs A or B” is satisfied under any of the foregoinginstances. In addition, the articles “a” and “an” as used in thisapplication and the appended claims should generally be construed tomean “one or more” unless specified otherwise or clear from context tobe directed to a singular form.

Moreover, terms such as “mobile device equipment,” “mobile station,”“mobile,” subscriber station,” “access terminal,” “terminal,” “handset,”“communication device,” “mobile device” (and/or terms representingsimilar terminology) can refer to a wireless device utilized by asubscriber or mobile device of a wireless communication service toreceive or convey data, control, voice, video, sound, gaming orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably herein and with reference to the relateddrawings. Likewise, the terms “access point (AP),” “Base Station (BS),”BS transceiver, BS device, cell site, cell site device, “Node B (NB),”“evolved Node B (eNode B),” “home Node B (HNB)” and the like, areutilized interchangeably in the application, and refer to a wirelessnetwork component or appliance that transmits and/or receives data,control, voice, video, sound, gaming or substantially any data-stream orsignaling-stream from one or more subscriber stations. Data andsignaling streams can be packetized or frame-based flows.

Furthermore, the terms “device,” “communication device,” “mobiledevice,” “subscriber,” “customer entity,” “consumer,” “customer entity,”“entity” and the like are employed interchangeably throughout, unlesscontext warrants particular distinctions among the terms. It should beappreciated that such terms can refer to human entities or automatedcomponents supported through artificial intelligence (e.g., a capacityto make inference based on complex mathematical formalisms), which canprovide simulated vision, sound recognition and so forth.

Embodiments described herein can be exploited in substantially anywireless communication technology, comprising, but not limited to,wireless fidelity (Wi-Fi), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), worldwideinteroperability for microwave access (WiMAX), enhanced general packetradio service (enhanced GPRS), third generation partnership project(3GPP) long term evolution (LTE), third generation partnership project 2(3GPP2) ultra mobile broadband (UMB), high speed packet access (HSPA),Z-Wave, Zigbee and other 802.XX wireless technologies and/or legacytelecommunication technologies.

Systems, methods and/or machine-readable storage media for facilitatinga two-stage downlink control channel for 5G systems are provided herein.Legacy wireless systems such as LTE, Long-Term Evolution Advanced(LTE-A), High Speed Packet Access (HSPA) etc. use fixed modulationformat for downlink control channels. Fixed modulation format impliesthat the downlink control channel format is always encoded with a singletype of modulation (e.g., quadrature phase shift keying (QPSK)) and hasa fixed code rate. Moreover, the forward error correction (FEC) encoderuses a single, fixed mother code rate of ⅓ with rate matching. Thisdesign does not take into the account channel statistics. For example,if the channel from the BS device to the mobile device is very good, thecontrol channel cannot use this information to adjust the modulation,code rate, thereby unnecessarily allocating power on the control channelSimilarly, if the channel from the BS to the mobile device is poor, thenthere is a probability that the mobile device might not able to decodethe information received with only the fixed modulation and code rate.As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, machine-readable media,computer-readable (or machine-readable) storage/communication media. Forexample, computer-readable media can comprise, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media. Of course, thoseskilled in the art will recognize many modifications can be made to thisconfiguration without departing from the scope or spirit of the variousembodiments.

It is to be appreciated and understood that components (e.g.,communication device, slice component, service network, core network,mobile service network, mobile core network, mobile network device,movable component, base station, cell, communication network, processorcomponent, data store, . . . ), as described with regard to a particularsystem or method, can include the same or similar functionality asrespective components (e.g., respectively named components or similarlynamed components) as described with regard to other systems or methodsdisclosed herein.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the subject matter has been described herein inconnection with various embodiments and corresponding figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: initiating,via a mobile network device, a wireless communication connection betweena device and a network device of a communication network; and generatinga service slice of a service network associated with the communicationnetwork, wherein the service slice and the wireless communicationconnection are utilized to facilitate generation of a securecommunication channel to securely communicate information between thedevice and a service network device of the service network, and wherein,in accordance with a defined security criterion relating to a servicethat is provided by the service network, the secure communicationchannel provides a first level of information communication securitythat is higher than a second level of information communication securityprovided by a portion of the communication network that does not includethe secure communication channel
 2. The system of claim 1, wherein thewireless communication connection is a first wireless communicationconnection, wherein the mobile network device is located in sufficientlyclose proximity to the device to enable establishing a second wirelesscommunication connection between the device and the mobile networkdevice, and wherein the first wireless communication connectioncomprises the second wireless communication connection.
 3. The system ofclaim 1, wherein the operations further comprise: generating a coreslice of a core network of the communication network, wherein the coreslice is associated with the service slice, wherein the service sliceand the core slice facilitate the generation of the secure communicationchannel between the device and the service network device, in accordancewith the defined security criterion.
 4. The system of claim 1, whereinthe defined security criterion relates to an information communicationsecurity protocol of a group of information communication securityprotocols comprising a medical-related information communicationsecurity protocol, a military-related information communication securityprotocol, a law enforcement-related information communication securityprotocol, an agriculture-related information communication securityprotocol, or a farming-related information communication securityprotocol, and wherein the operations further comprise: communicating theinformation securely between the device and the service network devicebased on the information communication security protocol.
 5. The systemof claim 1, wherein the operations further comprise: instantiating avirtual network function associated with the service slice and theservice to facilitate the secure communication of the informationbetween the device and the service network device.
 6. The system ofclaim 1, wherein the operations further comprise: in response todetermining that, during a first time period, a communication connectionbetween the device and the network device is not able to be established:establishing a connection portion of the wireless communicationconnection between the device and the mobile network device; andgenerating an internal service slice of a mobile service network,wherein the internal service slice and the connection portion of thewireless communication connection are utilized to facilitate securecommunication of an information portion of the information between thedevice and a mobile service network device of the mobile servicenetwork, in accordance with the defined security criterion.
 7. Thesystem of claim 6, wherein the operations further comprise:instantiating a virtual network function associated with the internalservice slice and the service to facilitate the secure communication ofthe information portion between the device and the mobile servicenetwork device.
 8. The system of claim 6, wherein the operations furthercomprise: via the internal service slice, receiving the informationportion from the device; and storing the information portion in a mobiledatabase component associated with the internal service slice and themobile network device.
 9. The system of claim 6, wherein the operationsfurther comprise: during a second time period, in response todetermining that the wireless communication connection between thedevice and the network device is able to be established, establishing,via the mobile network device, the wireless communication connectionbetween the device and the network device, wherein the service slice ofthe service network is generated in connection with the establishing ofthe wireless communication connection; and communicating the informationportion between the mobile network device and the service network deviceto facilitate synchronizing the information portion between the mobilenetwork device and the service network device in connection with theservice.
 10. The system of claim 1, wherein the mobile network deviceand a slice component, comprising a mobile database component, areassociated with a movable component comprising a vehicle or a motorizeddevice, wherein the movable component is operable to move betweenlocations, comprising a first location and a second location, tofacilitate moving the mobile network device and the slice component fromthe first location to the second location to place the mobile networkdevice and the slice component in proximity to the device, wherein,while at the second location, the slice component initiates the wirelesscommunication connection and generates the service slice, and whereinthe mobile database component stores an information portion of theinformation that is associated with the service network, including theservice.
 11. The system of claim 10, wherein the device is located in athird location in proximity to the mobile network device, and wherein,while the device is located in the third location, the network device isnot able to provide wireless communication service to the device withoututilizing the mobile network device to initiate the wirelesscommunication connection and generate the service slice to facilitateproviding the wireless communication service to the device.
 12. Amethod, comprising: facilitating, by a system comprising a processor,establishing a wireless connection between a device and a network devicevia a mobile network device, wherein the network device is part of acommunication network; and generating, by the system, a service slice ofa service network that is associated with the communication network,wherein the service slice and the wireless connection are utilized tofacilitate generating a secure communication channel usable to securelycommunicate data between the device and a service network device of theservice network, and wherein, in accordance with a defined securitycriterion relating to a service that is facilitated by the servicenetwork, the secure communication channel provides a first data securitylevel that is higher than a second data security level provided by aportion of the communication network.
 13. The method of claim 12,wherein the wireless connection is a first wireless connection, andwherein the method further comprises: based on the mobile network devicebeing located within a defined distance of the device, establishing, bythe system, a second wireless connection between the device and themobile network device via the mobile network device, wherein the firstwireless connection comprises the second wireless connection.
 14. Themethod of claim 12, wherein the defined security criterion relates to adata security protocol of a group of data security protocols comprisinga medical-related data security protocol, a military-related datasecurity protocol, a law enforcement-related data security protocol, anagriculture-related data security protocol, or a farming-related datasecurity protocol, and wherein the method further comprises:communicating, by the system, the data securely between the device andthe service network device based on the data security protocol.
 15. Themethod of claim 12, further comprising: generating, by the system, acore slice of a core network of the communication network, wherein thecore slice is associated with the service slice; and based on theservice slice and the core slice, generating, by the system, the securecommunication channel between the device and the service network deviceto facilitate the secure communication of the data between the deviceand the service network device, in accordance with the defined securitycriterion.
 16. The method of claim 12, wherein the data comprises afirst data portion of the data and a second data portion of the data,and wherein the method further comprises: facilitating, by the system,communicating, via the secure communication channel, the first dataportion of the data from the device to the service network device,wherein the first data portion of the data is stored in a databasecomponent of the service network; and facilitating, by the system,communicating, via the secure communication channel, the second dataportion of the data from the service network device to the device. 17.The method of claim 12, wherein the data comprises update dataassociated with the service, and wherein the method further comprises:receiving, by the system, via a first channel portion of the securecommunication channel, the update data from the service network device;and communicating, by the system, via a second channel portion of thesecure communication channel, the update data to the device, wherein theupdate data relates to a software update associated with the service ora firmware update associated with the service.
 18. The method of claim12, further comprising: instantiating, by the system, a virtual networkfunction associated with the service slice and the service to facilitatethe secure communication of the data between the device and the servicenetwork device.
 19. A machine-readable storage medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: initiating, via a movable networkdevice, a wireless connection between a device and a network device of acommunication network; and creating a slice of a service network,wherein the slice and the wireless connection are usable to create asecure communication pathway to facilitate secure communication ofinformation between the device and a service network device of theservice network, wherein, in accordance with a defined securitycriterion relating to a service that is facilitated by the servicenetwork, the secure communication pathway provides a first informationsecurity level with respect to the information that is higher than asecond information security level provided by a portion of thecommunication network.
 20. The machine-readable storage medium of claim19, wherein the slice is a first slice, and wherein the operationsfurther comprise: creating a second slice of a core network of thecommunication network, wherein the second slice is associated with thefirst slice; and based on the first slice and the second slice, creatingthe secure communication pathway between the device and the servicenetwork device to facilitate the secure communication of the informationbetween the device and the service network device, in accordance withthe defined security criterion.